Kibana stack monitoring: Normalized vs not-normalized CPU utilization

After compering CPU utilization in Kibana Stack monitoring and other tools my conclusion is that for default config:

  • Filebeat CPU utilization is not normalized, meaning for 4 cores the utilization goes from 0% to 400%
  • Elasticsearch CPU utilization on the other hand is normalized, i.e. for 4 cores it goes from 0% to 100%

Can someone confirm my assumption?
if this is default behavior, it's pretty confusing.

Hey, I suspect this post belongs in the beats group.
There you will get help from the relevant team members.

Thanks,
Liza

created separate posts for Elasticsearch and Filebeat


This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.