-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REQUEST]: Critical path and aggregated critical path #2876
Comments
👋 @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:
Can you confirm if the aggregated critical path functionality is still working in v8.15.1? |
@dgieselaar just checked on edge-lite, It's blank on the transaction details page, I think there's something wrong in the UI, I had to add height to some containers to display it. |
@gbamparop do you know if this bug has been fixed? |
Actually, @smith , do you know if this bug is fixed? |
@bmorelli25 this is still happening ![]() |
@gbamparop just FYI: the aggregated critical path flamegraph view will be removed #212256 |
Thanks, please feel free to close the docs issue if it's no longer relevant. |
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
Collaboration
The documentation team will investigate the issue and create the initial content.
Point of contact.
Main contact: @dgieselaar
Stakeholders:
The text was updated successfully, but these errors were encountered: