Hello @lorenzo_milicia
Welcome to the community.
I am not sure if below blog can be helpful & are related to the issue you are facing :
Thanks! The memory heaps look familiar indeed.
Can you also remove the
processor?
The kubernetes provider is adding the metadata by default so you don't need the extra processor for this.
C.
opened 09:35AM - 25 Oct 22 UTC
bug
enhancement
Team:Cloudnative-Monitoring
As reported at https://github.com/elastic/beats/issues/33307, the kubernetes aut… odiscovery provider can lead to OOM kills for Beats Pods in clusters with specific type of workloads, ie Cronjobs.
The purpose of this issue is the following:
1. Consider making `add_resource_metadata.cronjob: false` the default since we know it's an "expensive" feature.
2. Document the nature of this setting and its implications
3. Consider improving the way we retrieve the objects or get the "owner" name by trimming the suffix of the Object's name ie: `hello` (the name of the cronjob) out of `hello-1234` (the name of the job).
For full context and previous analysis see the summary at https://github.com/elastic/beats/issues/33307#issuecomment-1290251145.
cc: @eedugon @gizas @jsoriano
Thanks!!