[REQUEST]: Critical path and aggregated critical path

[gbamparop]

Description

To further investigate the end-user impact of a given service and identify the time this service is on the critical path i.e. causing the end-to-end request to take more time to complete we have introduced a critical path view for individual traces and an aggregated critical path view calculated on a set of traces.

The feature is currently in technical preview and can be enabled through the APM Labs or Kibana advanced settings.

Critical path in the trace waterfall

Before critical path is enabled

After critical path is enabled

Aggregated critical path

Transaction details page

Trace explorer

When trace explorer is enabled the aggregated critical path is displayed in a separate tab.

Resources

• https://github.com/elastic/apm-dev/issues/985 (Proposal to add critical path analysis in dependency operations and change the release target to Beta.
• https://github.com/elastic/apm-dev/issues/838
• https://github.com/elastic/kibana/issues/142370
• https://github.com/elastic/apm-dev/issues/759
• https://github.com/elastic/apm-dev/issues/759
• https://github.com/elastic/app-obs-dev/issues/27
• https://github.com/elastic/apm-trace-aggregation

Collaboration

The documentation team will investigate the issue and create the initial content.

Point of contact.

Main contact: @dgieselaar

Stakeholders:

• @gbamparop
• @AlexanderWert
• @akhileshpok

[colleenmcginnis]

👋 @gbamparop @dgieselaar I'm able to use the critical path view in the trace sample timeline with no problems. The Aggregated critical path tab is still there, but when I click it:

• On the Transaction details page it renders a blank box

• On the Trace explorer I just see a spinning loading icon

  Can you confirm if the aggregated critical path functionality is still working in v8.15.1?