-
Notifications
You must be signed in to change notification settings - Fork 166
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]: Universal Profiling within Hosts #3481
Comments
@iogbole FYI I'm seeing whether the docs team needs to update the Host documentation to explain this within the context of hosts |
@roshan-elastic is this going live in 8.12 without a feature flag? |
Hey @bmorelli25 - there will be a feature flag so users can turn it off but it will be on by default. @mykolaharmash - Would you mind confirming your current understanding? Just want to check I'm right about this (if I'm wrong, we can pick up separately). |
You're correct @roshan-elastic 💯 |
@bmorelli25 cool gif here demo'ing it: |
Closing this one as the docs PR was merged 🎉 |
Description
What?
We will be integrating Universal Profiling into the Hosts views
When?
8.12 (TBC whether this will be turned on/off by default - it can be controlled by a feature flag)
Why?
Users who are investigating high CPU usage on a host want to know what is consuming this CPU. Profiling helps users identify the exact usage...right down to the single line of application code.
This will help users:
(a) Resolve utilisation issues with their hosts quicker by identifying the root cause of the resource usage
(b) Help users optimise their application code to be more performant and reduce their overall infrastructure costs
Resources
Screenshot
General profiling documentation
Which documentation set does this change impact?
Stateful only
Feature differences
At the time of writing, profiling is only available in stateful and for cloud customers (not self-managed)
What release is this request related to?
N/A
Collaboration model
The documentation team
Point of contact.
Main contact: @roshan-elastic (PM)
Stakeholders: @iogbole (PM) @smith
The text was updated successfully, but these errors were encountered: