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.
In a flame graph it sometimes can be quite tricky to spot the part of the code/component you actually want to investigate on: A component might serve multiple roles, but you are only interested in one of them.
Describe the solution you'd like
In the same way that we can currently focus on a box in the flame graph or row in the table, we should be able to hide stacks that pass through that box/row.
Alternatives considered
Filtering on collection could be an option, but ideally there should be a very dynamic way of hiding aspects the user is not interested in. Also filter on collection is not reverseable, so there is no way to know when the filter hide the actual problem.
Additional context
This is likely something we need to modify the flame graph component in Grafana itself.
The text was updated successfully, but these errors were encountered:
Feature description
Is your feature request related to a problem? Please describe.
In a flame graph it sometimes can be quite tricky to spot the part of the code/component you actually want to investigate on: A component might serve multiple roles, but you are only interested in one of them.
Describe the solution you'd like
In the same way that we can currently focus on a box in the flame graph or row in the table, we should be able to hide stacks that pass through that box/row.
Alternatives considered
Filtering on collection could be an option, but ideally there should be a very dynamic way of hiding aspects the user is not interested in. Also filter on collection is not reverseable, so there is no way to know when the filter hide the actual problem.
Additional context
This is likely something we need to modify the flame graph component in Grafana itself.
The text was updated successfully, but these errors were encountered: