Open tetianakravchenko opened 2 days ago
This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @tetianakravchenko? 🙏. For such, you'll need to label your PR with:
To fixup this pull request, you need to add the backport labels for the needed branches, such as:
backport-v8./d.0
is the label to automatically backport to the 8./d
branch. /d
is the digitThe fields definition must be updated as well in https://github.com/elastic/beats/blob/c2b2983c1825dcf7dabf64c4a04ce9cf34814fce/metricbeat/module/kubernetes/pod/_meta/fields.yml#L59. And also make update
needs to be run to update the docs.
Proposed commit message
kubernetes.pod.cpu.usage.limit.pct
andkubernetes.pod.memory.usage.limit.pct
If any container of the Pod does not have cpu limit defined:kubernetes.pod.cpu.usage.limit.pct
will not be reported, similar for the memory:kubernetes.pod.memory.usage.limit.pct
andmemory.working_set.limit.pct
will not be reported This implementation is similar to https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/v0.103.0/receiver/kubeletstatsreceiver/internal/kubelet/metadata.go#L113-L116Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
-
Use cases
Screenshots
Logs