We have a pod running the module kubernetes in our openshift cluster. We had upgraded metricbeat from 6.2.4 to 6.4.0. We have noticed that metricbeat 6.4.0 consummates 3 times cpu than 6.2.4.
Here is our the metricbeat config. Is there any reason ?
We introduced automatic enriching for all Kubernetes metricsets. That means that every monitored resource events (for instance, replicaset metrics) get enriched with labels and annotations from that resource.
You can disable that behavior by setting add_metadata: false in the module settings.
Sorry for the delay. I'll give you a complete feedback when we'll upgrade our RUN cluster. At now, we seen that on our BUILD cluster, now in 6.4 and I don't want downgrade in 6.2.
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.