-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Profiling] Add colors for new frame types (process name, thread name, root) #204977
[Profiling] Add colors for new frame types (process name, thread name, root) #204977
Conversation
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff Tim! 🚀 thanks 🙏🏼
d0a4cf4
to
1758e7a
Compare
d9acea6
to
14391a0
Compare
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
History
cc @rockdaboot |
…, root) (elastic#204977) ## Summary This PR is a pre-requisite for adding aggregation by process name and by thread name to the Universal Profiling flamegraph view. It adds three artificial node types to the flamegraph including color codes. As a side-effect, the root node now has its own color code. Previously, it (accidentally) used the color code of "unknown" type frames. The PR is backwards compatible, so it doesn't change anything in the UI when connecting with current Elasticsearch. As soon as [the PR for ES](elastic/elasticsearch#119115) is merged, the new aggregations show up.
Summary
This PR is a pre-requisite for adding aggregation by process name and by thread name to the Universal Profiling flamegraph view.
It adds three artificial node types to the flamegraph including color codes.
As a side-effect, the root node now has its own color code. Previously, it (accidentally) used the color code of "unknown" type frames.
The PR is backwards compatible, so it doesn't change anything in the UI when connecting with current Elasticsearch.
As soon as the PR for ES is merged, the new aggregations show up.