[APM] Action menu: Link trace.id to Logs UI

[makwarth]

Edit: 3/26/2019: Updating description as original description didn't make any sense.

Add link to transaction Actions menu: Show trace logs. The link will take the user to the Logs UI, filtered by a text search on the value of trace.id. Let's discuss if the link should be conditional or static.

Example:

[elasticmachine]

Pinging @elastic/apm-ui

[makwarth]

Blocked by #23316

[alvarolobato]

Felix is planing to put some work on this one (#23316) soon to allow liking from Monitoring, which should unblock this.

[jasonrhodes]

@alvarolobato @makwarth We currently have a list of links that get created based on the current transaction we're viewing in the "Actions" dropdown. Can we add detail to this ticket description to explain when we want to include the trace ID, for which links? All links in the actions dropdown, or a new link, etc? Thanks!

[jasonrhodes]

@weltenwort I'm looking at this as well a comment you and Alvaro made earlier this week in Slack:

Alvaro: Links on the dev environment from APM to infra UI seem to be broken, did anyone see it?

Felix: looks like APM is linking to a host even though the entity is a k8s pod, and it still uses the pod name instead of the uid

Can you give me some more context on this and how I could reproduce it? I need to get more familiar with the infra side, maybe a zoom would be useful on Monday if you have time. Thanks!

[weltenwort]

I saw from the URL that @alvarolobato shared, that it is a link to metrics of a host with the host id looking like a k8s pod name. When navigating to that URL, the Infra UI in Kibana reponds with an error message that no such host exists. Two things seem to contribute to that problem here:

• The links to metrics and logs in the "actions" menu try to show the "Host logs" and "Host metrics" using the k8s pod name and not the underlying hostname.
• Even if the links referred to "pods" instead of "hosts", these are referred to using their ids and not names, since those are not well suited as a unique identifier.

[jasonrhodes]

Let's discuss if the link should be conditional or static.

We decided via Slack conversation to make this link work like all the others, i.e. conditional on the value it requires for the link (trace.id here)

[jasonrhodes]

@makwarth I see you only mention the logs UI here but the other links in this menu all come in pairs, one to logs and one to metrics. Is that on purpose?

I'm also checking to see if it's possible to link to the logs only by trace ID, because the linked ticket only mentions trace ID being possible as a secondary filter (the examples all do link-to/host-metrics/{host}?filter=trace.id=whatever etc)

[makwarth]

@jasonrhodes Yes, since CPU/Mem metrics documents don't have trace.id

[jasonrhodes]

@makwarth ah yes, good reason! :)