-
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
[Stack Monitoring] Use cgroup metrics for Beats and APM Server CPU/memory usage #79050
Comments
We can work on this for the next minor. However, I'm not seeing this data showing up in 7.10 cloud instances. I'm assuming it should be working there. To be clear, the fields are present but the values are all |
Opened elastic/beats#22844 regarding the zero values issue. |
Add field mappings for the cgroups metrics added to beats monitoring in elastic/beats#21113, and required by elastic/kibana#79050.
Add field mappings for the cgroups metrics added to beats monitoring in elastic/beats#21113, and required by elastic/kibana#79050.
Mappings are updated (thanks for the review @chrisronline, I hope I wasn't too presumptuous in asking) and backported to 7.x. Just waiting on a final review of the beats changes before we can pull that into apm-server. |
@chrisronline the Kibana changes did not make it for 7.11, due to the issues you found - is that right? The ES mappings and apm-server fix were both merged in for 7.11, so should we relabel this for 7.12 now? |
Hi @axw, It doesn't look it made 7.11, but we will prioritize it for 7.12 |
cc: @elastic/stack-monitoring Are the changes for this checked in the SM UI for 7.12 yet? |
Not yet, but it will be done for 7.12 |
Add field mappings for the cgroups metrics added to beats monitoring in elastic/beats#21113, and required by elastic/kibana#79050.
Add field mappings for the cgroups metrics added to beats monitoring in elastic/beats#21113, and required by elastic/kibana#79050.
Describe the feature:
Update Stack Monitoring to use the cgroup metrics recently added to Beats: elastic/beats#21113. Once elastic/apm-server#4249 is merged, apm-server will too. Stack Monitoring should use these for calculating more accurate CPU and memory usage when running Beats and APM Server in containers.
Describe a specific use case for the feature:
From elastic/beats#14691:
Example monitoring document:
(apm-server specific fields omitted for brevity.)
The text was updated successfully, but these errors were encountered: