[APM] Prototype backend service operations/span.name breakdown and ability to link to traces

[dannycroft]

Todays view into dependencies (backend services like databases, cache, storage, etc) does not provide a granular breakdown into the operations/queries executed, impact and performance trends overtime.

This issue is to prototype using existing sampled span and transaction data we have to improve the depenedency granularity.

Mock Ups

List of operations:

Link of traces with drill down into end-to-end trace:

Note: Mockups are a guidance and not a requirement

Issue Tracking

• [APM] Display list of operations for dependency #133478
• [APM] Detail view for backend operation #133479
• [APM] Latency chart for backend operation detail view #133480
• [APM] Throughput chart for backend operation detail view #133481
• [APM] Error rate for backend operation detail view #133482
• [APM] Latency distribution chart for backend operation detail view #133483
• [APM] Operations table for backend operation detail view #133484

Links

• https://github.com/elastic/apm-dev/issues/715 (Internal)
• https://github.com/elastic/observability-product/issues/119 (Internal)

[elasticmachine]

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