-
Notifications
You must be signed in to change notification settings - Fork 1.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
Support docker.kmem.usage #3339
Conversation
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.
Thank a lot for this contribution 💯. It is really appreciated!
Looks good to me but I would like @DataDog/container-integrations to approve as well.
Hi @wolf31o2 , Thanks again for the contribution! So, if you are using the Agent 6, you won't get this metric if we merge it right now. You can take a look at this PR: DataDog/datadog-agent#2952 this is a good example on how to add a docker metric for the agent 6. Also, please add your new metric to the metadata file, it will be used in our documentation: Thanks! |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community. |
Hi @wolf31o2 Thanks |
Sorry, I'm aware that this is for agent 5. As I said, we're using this in production. |
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.
Thanks for clarifying @wolf31o2
Could you update the metadata.csv file in the same folder with this new metric then? This will make it easily discoverable in the Datadog UI, add a description for everyone to see, and make the unit scale nicely on graphs.
Sure. :-) |
Some recent versions of Docker perform Kernel Memory accounting. Because of this, it's necessary to monitor a container's Kernel Memory usage. This gives us a GAUGE counter to determine kernel memory. This has been in use in production on our site for 6 months. Signed-off-by: Chris Gianelloni <[email protected]>
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.
brilliant, thanks @wolf31o2 !
Some recent versions of Docker perform Kernel Memory accounting. Because
of this, it's necessary to monitor a container's Kernel Memory usage.
This gives us a GAUGE counter to determine kernel memory. This has been
in use in production on our site for 6 months.
Signed-off-by: Chris Gianelloni [email protected]
What does this PR do?
Adds metrics collection for Docker container Kernel memory usage.
Motivation
Running Docker versions > 1.13 on RHEL-based kernels enabled kernel memory process accounting. However, this used the old cgroup v1 interface, which was essentially broken. To properly size container limits, accounting of the container's kernel memory usage was required.
Additional Notes
This is fairly simple and doesn't touch existing functionality.
Review checklist (to be filled by reviewers)
changelog/
andintegration/
labels attached