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

receiver/dockerstats: add more metrics #22037

Closed
2 tasks done
gbbr opened this issue May 17, 2023 · 10 comments
Closed
2 tasks done

receiver/dockerstats: add more metrics #22037

gbbr opened this issue May 17, 2023 · 10 comments
Assignees
Labels

Comments

@gbbr
Copy link
Member

gbbr commented May 17, 2023

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:

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.PrivateWorkingSet
  • container.memory.commit: available in MemoryStats.Commit
  • container.memory.commit_peak: available in MemoryStats.CommitPeak
  • container.pid.thread_count: available in PidStats.Current
  • container.pid.thread_limit: available in PidStats.Limit
  • container.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.

@gbbr gbbr added enhancement New feature or request needs triage New item requiring triage labels May 17, 2023
@github-actions
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@gbbr gbbr changed the title receivers/dockerstats: add more metrics receiver/dockerstats: add more metrics May 17, 2023
@jamesmoessis
Copy link
Contributor

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".

container.cpu.limit already has a PR up here: #21803

For uptime, please follow the guidance of the semantic convention regarding this metric.

container.pid.thread_count & container.pid.thread_limit can be renamed to container.pid.threads.count and container.pid.threads.limit.

Please ping me once you have a PR up :)

@gbbr
Copy link
Member Author

gbbr commented May 23, 2023

Thank you for looking James. I will start with a PR for container.uptime, and continue with the rest as per your instructions.

@github-actions
Copy link
Contributor

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jul 31, 2023
@mx-psi
Copy link
Member

mx-psi commented Jul 31, 2023

@gbbr can this be closed?

@gbbr
Copy link
Member Author

gbbr commented Jul 31, 2023

Not yet, I'm going to work on adding some more of these.

@mx-psi mx-psi removed the Stale label Jul 31, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 2023

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Oct 2, 2023
@mx-psi mx-psi removed the Stale label Oct 2, 2023
@gbbr
Copy link
Member Author

gbbr commented Oct 2, 2023

Still being worked on in #21803

Copy link
Contributor

github-actions bot commented Dec 4, 2023

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Dec 4, 2023
@mx-psi
Copy link
Member

mx-psi commented Dec 4, 2023

#21803 has been merged so I am closing this :)

@mx-psi mx-psi closed this as completed Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants