[APM] Service overview: Change the instance links for any language other than Java to filter the Metrics page by service.node.name

[formgeist]

Summary

Since all agents other than Java only have the default Metrics page without instance detail pages, I would suggest a small enhancement to the links from the Instances table. Linking to the Metrics page, but use the selected service.node.name would filter the Metrics page by that instance.

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[sorenlouv]

I think this is a good enhancement in the short term. Ideally, I'd think all languages should behave the same, meaning that we'd get an instance overview page and instance details page everywhere and not just for java.

[formgeist]

@sqren Yeah, there's an updated instances view in the works but it's a larger overhaul, so it'll be some time before we're there.

[dgieselaar]

I actually implemented this but looks like it broke in #86986 when MetricOverviewLink started using EuiLink instead of APMLink. See

kibana/x-pack/plugins/apm/public/components/app/service_overview/service_overview_instances_table/index.tsx

Line 78 in 5b31585

<MetricOverviewLink

[sorenlouv]

but it's a larger overhaul

Perhaps exactly for this reason we should clean it up now. Right now we have duplicated the logic for java vs the other languages. I suggest that we remove one of the implementations - preferably the non-java implementation.

[sorenlouv]

Currently the overview page for java looks like this:

We can make the columns conditional so for the other languages they just show CPU and Memory (for now at least - I'm sure down the line we want to add more metrics for them as well).

[formgeist]

Discussed this at refinement yesterday, we've decided to only fix the linking from non-JVM instances to filter the Metrics view by the selected instance ID instead of implementing a larger overhaul of the Metrics view for non-Java language agents in lieu of the Service instance design that is going on at the moment.