-
Notifications
You must be signed in to change notification settings - Fork 31
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
Please allow for a blacklist/whitelist when it comes to the chef tags that DataDog sends with it's data. #85
Comments
I think this could be a way to fix it, but I'm not sure. (note this is ruby and c# mixed together because I'm not all that fluent with ruby yet)
|
I'd need these questions answered though:
|
👍 |
This would definitely clean up the tags list. |
This would make the tags in DD so much more useful to me! Right now they are more hurtful than they are helpful. |
Thanks @ABrehm264 for your feedback!
Your approach would fix this indeed. The environment and role tags (
Sounds reasonable yes!
You could pass the regex to the And just to be extra clear: filtering the list of tags that's sent to Datadog would not only affect the event tags but also the host-level tags. This means that all the metrics and service checks coming from the host/Agent would also stop being tagged with these excluded tags. Let me know if you have any questions or if you need help with the implementation, thanks! |
@olivielpeau, I think I got it, can you check over it and let me know if it's good? If it's good, what are the next steps?
and the travis-ci problems on the chef-handler-datadog are probably related to bundler pulling the bleeding edge versions of some gems. I'm not really sure how to test the integration between chef-datadog and chef-handler-datadog though. |
@olivielpeau, I changed the test name that you asked be changed per https://github.com/DataDog/chef-handler-datadog/pull/86/files#r75447388. Thanks, |
… tags that the host sends to datadog
I have several tags that are super useful for me to have in chef, but not so useful when it's sent to DataDog to be read by my developers, since they end up turning into noise. Would it be possible to blacklist/whitelist the tags the chef sends using a regex or something?
Example:
My server has these tags:
When events or event log entries are sent, every one is tagged with every single chef tag associated with the box.
I would like to make it so that it either sends no chef tags or it only sends the ENV_ tag.
The text was updated successfully, but these errors were encountered: