-
Notifications
You must be signed in to change notification settings - Fork 71
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
Some metrics cannot be excluded #403
Comments
Same problem here. In our scenarios, we don't care about In Legacy monitoring agent we configured collectd this way, however we don't find an option to do the same in the new Ops Agent.
|
Only being able to exclude a directory of metrics at a time is currently WAI. |
I had the same issues with /dev/loop* devices and because it gets really expensive I decided to fork the agent to exclude them by default. The ideal scenario would probably be to be able to override the default Or even better, be capable of defining several time the hostmetrics receiver like it's possible to do with opentelemetry-collector where you can define different frequencies depending on the metrics: |
Hello, we are using this config
The
agent.googleapis.com/processes/*
exclusion and other ones with 2 path components (not including the/*
) work but exclusions with 3 path components do not work (likeagent.googleapis.com/memory/bytes_used/*
)Being excluded correctly:
Not being excluded:
I'm assuming the problem here is that metrics like
agent.googleapis.com/disk/read_bytes_count/*
do not branch out anymore so the ending/*
is a problem because it expects it to branch out more, removing/*
throws an error when starting the google-cloud-ops-agent as it's hardcoded to require it hereMetrics like
agent.googleapis.com/processes/*
are getting excluded because they branch out intoagent.googleapis.com/processes/count_by_state
so the/*
matchesThe text was updated successfully, but these errors were encountered: