Kibana: [APM] Make the errors on the Trace summary clickable

[nehaduggal]

In the APM App Trace view, the number of errors in a trace is surfaced up top and in the individual transaction fly out but the clickable error links are only on the annotation on the timeline. Although the timeline error clicks are great, they are sometimes hard to discover.

For the Error count that appear in the Traces view in the summary, we should allow a user to click on it. Clicking on it should take the user to the Errors view that is filtered for the errors that pertain to the corresponding trace.

Similarly, in the transaction fly out view the error on on the transaction summary view should allow for navigation to the errors UI filtered to the error captured for that transaction.

[elasticmachine]

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

[formgeist]

Clicking on it should take the user to the Errors view that is filtered for the errors that pertain to the corresponding trace.

Unfortunately, this will only result in the errors for the selected service (or the root transaction) which means the count will not match because we're adding up all the errors for all transactions by _all_ services in that summary.

Similarly, in the transaction fly out view the error on on the transaction summary view should allow for navigation to the errors UI filtered to the error captured for that transaction.

This is a good catch 👍

[formgeist]

Not sure if we're going to solve this any time soon if we're not thinking about creating a service-agnostic Errors view (similar to Traces) where we can list the related errors for a trace.id across multiple services. @nehaduggal WDYT - do you see this on the roadmap anytime soon?

[nehaduggal]

It would be nice to have a new errors experience similar to the existing traces view. We can create a separate meta issue to track that and discuss priority there.

To fix the issue above(for now), as long as there is just 1 error, we should allow the user to click and navigate to the error. If there are multiple errors we can add a tool tip(on hover/click) to guide a user to click on the individual errors on the timeline. While the tooltip is not an ideal experience, it will help discoverability of the errors on the timeline.

[sqren]

@nehaduggal Sounds like a good intermediary solution until we can have something like this:

[formgeist]

To fix the issue above(for now), as long as there is just 1 error, we should allow the user to click and navigate to the error. If there are multiple errors we can add a tool tip(on hover/click) to guide a user to click on the individual errors on the timeline. While the tooltip is not an ideal experience, it will help discoverability of the errors on the timeline.

Yeah, sounds like a reasonable compromise for now. I'll mock up how this will look and let us it move forward.

@nehaduggal Will you open a separate issue for tracking the design of the global Errors experience? Thanks