Describe the enhancement:
All Beats report CPU usage stats via the GET stats API endpoint (when the Beat is running with http.enabled: true). Currently, these do not account for the Beat running in a container. The Elasticsearch Node Stats API and the Logstash Node Stats API both return additional os.cgroup.* metrics when running in a container. We should consider doing something similar for Beats as well.
Describe a specific use case for the enhancement or feature:
The Stack Monitoring UI can take advantage of these metrics and display CPU usage more accurately, depending on whether the Beat is running in a container or not. It already does this for Elasticsearch (see https://www.elastic.co/guide/en/kibana/current/monitoring-settings-kb.html#monitoring-ui-cgroup-settings).
Describe the enhancement:
All Beats report CPU usage stats via the
GET statsAPI endpoint (when the Beat is running withhttp.enabled: true). Currently, these do not account for the Beat running in a container. The Elasticsearch Node Stats API and the Logstash Node Stats API both return additionalos.cgroup.*metrics when running in a container. We should consider doing something similar for Beats as well.Describe a specific use case for the enhancement or feature:
The Stack Monitoring UI can take advantage of these metrics and display CPU usage more accurately, depending on whether the Beat is running in a container or not. It already does this for Elasticsearch (see https://www.elastic.co/guide/en/kibana/current/monitoring-settings-kb.html#monitoring-ui-cgroup-settings).