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

exclude a container check #11

Closed
xueshanf opened this issue Dec 5, 2014 · 4 comments
Closed

exclude a container check #11

xueshanf opened this issue Dec 5, 2014 · 4 comments

Comments

@xueshanf
Copy link

xueshanf commented Dec 5, 2014

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

  include: []
  exclude:
     - "image:example.com/itlab/s3sync:latest"
     - "example.com/itlab/s3sync:llatest"
     - ".*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?

@LotharSee
Copy link
Contributor

Hi @xueshanf,
Thanks for this report! It's definitively a bug: the filter doesn't apply to events. It only applies to metrics.

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.

@LotharSee
Copy link
Contributor

Thanks for the screenshot! It's making this easier.
However we are reporting metrics per host / per container. So maybe this specific container wasn't reporting.
Can you display the graph with the option "One graph per" then you pick "name" (or "container_name", depending on your Agent version). Then you will see one graph per container, running on this host.
If the one filtered isn't there, it means that it got properly filtered!

@xueshanf
Copy link
Author

xueshanf commented Dec 5, 2014

@LotharSee,

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.

cpu-per-container

I have done some changes, here is the recap of the platform info:

  1. CoreOS

  2. docker-dd-agent: latest

  3. Conf.d:

    # include all, except awscli
    include: []
    exclude:
      - "name:s3sync"
      - "image:.*awscli"
    #
    

@LotharSee
Copy link
Contributor

Thanks for this detailed explanation.
This way I was able to open an issue on the Agent project: DataDog/dd-agent#1234

I'll close this one, you can follow this issue and I'll notify you there once it's fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants