-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[receiver/kubeletstats] Add new memory utilization metrics #25894
[receiver/kubeletstats] Add new memory utilization metrics #25894
Conversation
A good comment was brought in the issue: #24905 (comment). Let's discuss that first. |
@dmitryax if you feel good about the |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
SGTM |
@dmitryax updated the names and implemented |
6fe5916
to
e9f8810
Compare
@dmitryax this is ready for a proper review. |
@dmitryax ready for review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
…metry#25894) **Description:** Adds new `k8s.pod.memory.utilization` and `container.memory.utilization` metrics that represent the ratio of memory used vs limits set. The metrics are only emitted for pods/containers that have defined resource limits. It takes advantage of the pod metadata to acquire the container limits. A pod limit is computed as the sum of all the container limits and if any container limit is zero or undefined the pod limit is also considered undefined. **Link to tracking Issue:** Related to open-telemetry#24905 **Testing:** Unit tests and local testing
Description:
Adds new
k8s.pod.memory.utilization
andcontainer.memory.utilization
metrics that represent the ratio of memory used vs limits set.The metrics are only emitted for pods/containers that have defined resource limits. It takes advantage of the pod metadata to acquire the container limits. A pod limit is computed as the sum of all the container limits and if any container limit is zero or undefined the pod limit is also considered undefined.
Link to tracking Issue:
Related to #24905
Testing:
Unit tests and local testing