You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently in order to view trace profiles, it is required to use the "Classic Explore -> Pyroscope" view. Under query options it allows to filter by a known span id. Otherwise there is not mechanism to discover span id, they will almost likely always come from a deeplink out of the "Classic Explore -> Traces" view.
I would like to replace the Classic Explore fully with "Explore Profiles" and there for being able to filter profiles by span ID. It would also nice, if the Explore Profiles could list traces involved by the profile on show. (Backend feature is tracked in grafana/pyroscope#3289)
Alternatives considered
Describe alternatives you've considered
We could just stay with Classic Explore for longer
Additional context
Related
The text was updated successfully, but these errors were encountered:
Feature description
Is your feature request related to a problem? Please describe.
Currently in order to view trace profiles, it is required to use the "Classic Explore -> Pyroscope" view. Under query options it allows to filter by a known span id. Otherwise there is not mechanism to discover span id, they will almost likely always come from a deeplink out of the "Classic Explore -> Traces" view.
View in "Classic Explore -> Pyroscope":
Source of the link:
This is how the link looks like decoded:
Describe the solution you'd like
I would like to replace the Classic Explore fully with "Explore Profiles" and there for being able to filter profiles by span ID. It would also nice, if the Explore Profiles could list traces involved by the profile on show. (Backend feature is tracked in grafana/pyroscope#3289)
Alternatives considered
Describe alternatives you've considered
Additional context
Related
The text was updated successfully, but these errors were encountered: