-
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/dockerstats: add more metrics #22037
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hey @gbbr thanks for your interest in helping improve the docker stats receiver. Would be happy to review small, decoupled PRs. Probably one for memory, one for PID, and one for "other".
For uptime, please follow the guidance of the semantic convention regarding this metric.
Please ping me once you have a PR up :) |
Thank you for looking James. I will start with a PR for |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@gbbr can this be closed? |
Not yet, I'm going to work on adding some more of these. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Still being worked on in #21803 |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
#21803 has been merged so I am closing this :) |
Component(s)
receiver/dockerstats
Is your feature request related to a problem? Please describe.
There are a bunch of metrics available as part of the already used
internal/docker
package that could be exposed by the dockerstatsreceiver.Describe the solution you'd like
I would like to open a PR and add the following metrics:
container.uptime
: time.Since(ContainerState.StartedAt) (receiver/dockerstatsreceiver: add container.uptime metric #22851)container.cpu.limit
: can be computed based on the HostConfig CPU information ([receiver/dockerstats] Add inspect metrics #21803)Additionally, I would also be interested in adding these:
container.memory.failcnt
: OOM events (data is available in MemoryStats.FailCnt)container.memory.working_set
: available in MemoryStats.PrivateWorkingSetcontainer.memory.commit
: available in MemoryStats.Commitcontainer.memory.commit_peak
: available in MemoryStats.CommitPeakcontainer.pid.thread_count
: available in PidStats.Currentcontainer.pid.thread_limit
: available in PidStats.Limitcontainer.pid.open_files
: this one is not available, but we have a small "cgroups" module at Datadog that can help and it'd be easy to obtain the value.If any of these need more discussion, we can pull them out into their own issue.
The text was updated successfully, but these errors were encountered: