-
Notifications
You must be signed in to change notification settings - Fork 189
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
exclude a container check #11
Comments
Hi @xueshanf, Can you check if the Agent reports Docker metrics relative to this container? (you can for example, in the Metric Explorer, look at docker.cpu.user tagged by this container name). Then I'll open another issue on the Docker Check (https://github.com/DataDog/dd-agent) since it's not related to the container version of the Agent. |
Thanks for the screenshot! It's making this easier. |
Here is a screenshot with cpu per container metrics. It looks like the s3sync container was filtered out, but I am still seeing events data in datadog, they are not filtered out. I have done some changes, here is the recap of the platform info:
|
Thanks for this detailed explanation. I'll close this one, you can follow this issue and I'll notify you there once it's fixed! |
I have a container controlled by a timer unit. It runs every 30 seconds and I want to exclude it from the datadog agent check. The image is tagged as 'example.com/itlab/s3sync:latest'. I tried the following config:
conf.d/docker.yaml
....
include all, except s3sync
...
The exclude does not seem to work. I still see the events for this container that comes and go.
What's the correct format to exclude a container check?
The text was updated successfully, but these errors were encountered: