Can someone confirm that by using all default settings Filebeat CPU utilization metrics in Kibana stack monitoring are not normalized, e.g. for 4 CPUs the CPU utilization goes from 0% to 400%.
I answered Elasticsearch CPU utilization metrics are normalized by default but assumed you were talking about cpu percentage differences between what you see in Stack Monitoring and what you see in the Infra UI (or, what you see in .monitoring-es-* documents versus what you see in metricbeat-* documents).
Did I assume correctly? Or are you talking about monitoring Filebeat within the Stack Monitoring UI?
I traced through the Beats code and can confirm that the CPU usage reported to stack monitoring for a Beat is not normalized by number of cores. Details of my code trace are below.
Working backwards from the Stack Monitoring UI code to the Beats code:
Jumping through a couple more function calls, the value of that field is taken from here. As you can see a couple lines later, Beats actually does have access to the normalized CPU percentage value, but at the moment we are not sending it to stack monitoring, so the UI cannot use it.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.