-
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
add docker event receiver #29096
Comments
Please look at https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/dockerstatsreceiver |
I want to know about when these events happened, I will make a statistics on how many containers are created or destroyed, or send a alert about oom event.
It should be treated as log, for I need to know the container name or some other meta infomation like hostname, ip, etc. It may cause |
Pinging code owners for receiver/dockerstats: @rmfitzpatrick @jamesmoessis. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging dockerstats receiver codeowners in case they have an idea on the best path here. |
I think this would be useful functionality to add to the docker stats receiver as a logs receiver. Its core docker client already watches for a subset of container events in determining from which ones to pull stats. Since the OTel notion of events is in development but has effectively been formalized to use log records, it's possible that we'd be able to collaborate on future semantic conventions for the platform. https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/event-api.md |
Removing |
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. |
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. |
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. |
Component(s)
No response
Is your feature request related to a problem? Please describe.
I want to get container events
Describe the solution you'd like
I'd like to subscribe some docker event, such as
container create/stop
oom
Describe alternatives you've considered
New a docker client, and subscribe docker event
Additional context
No response
The text was updated successfully, but these errors were encountered: