Skip to content
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

[Docker Check] add kernel memory usage metric #3396

Merged
merged 1 commit into from
May 3, 2019

Conversation

wolf31o2
Copy link
Contributor

@wolf31o2 wolf31o2 commented May 1, 2019

What does this PR do?

Extends Docker check to provide Kernel Memory Usage Metric

Containers run under cgroups with kernel memory accounting enabled will consume kernel memory which needs to be tracked.

Motivation

Running Docker under CentOS 7 and hitting issues described in runc and Mesosphere DC/OS

Additional Notes

This metric will be zero under newer Docker (18.09) and CentOS 7 kernels. Running containers will memory limits (not kernel memory limits) under CentOS 7 with Docker 17.06 will account usage. Modern Docker on a modern kernel requires setting kernel memory limits when starting the container for this metric to take effect.

This is the Agent 6 implementation of DataDog/integrations-core#3339

@wolf31o2 wolf31o2 requested a review from a team as a code owner May 1, 2019 16:29
@bits-bot
Copy link
Collaborator

bits-bot commented May 1, 2019

CLA assistant check
All committers have signed the CLA.

@wolf31o2
Copy link
Contributor Author

wolf31o2 commented May 3, 2019

@hkaj can I get a review when you have time? I've addressed your comments.

Copy link
Member

@hkaj hkaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hkaj
Copy link
Member

hkaj commented May 3, 2019

thanks @wolf31o2 🎉

@hkaj hkaj merged commit 68b5802 into DataDog:master May 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants