Make it possible to add tags in the Datadog integration so I can tell my staging and production environments apart more easily
Datadog recommends having only one account and feed data from all environments into it, and then it’s important to tell them apart by using tags.
Please add the ability to set tags in the Datadog integration configuration, e.g. env:production
@andrewDavidson, Its been almost two years since you posted you will implement this in the future. Can you please get us a concrete ETA? At Indeed, we do have requirement to get the labels emitted on the UI as well as Datadog. The "env" is just one of several tags we need to display.
Looping @ulrich from your Team who we have meetings with every week.
This is exactly my problem. I need to be able to pass tags back to Datadog in order to distinguish my "env" key that I have as a label.
Since project name is emitted, one temporary workaround I see is to add suffix to the project name for the value of "env" variable. But this is a non-standard practice since for every service we use the "env" tag in Datadog.
I'd be also heavily interested in that feature as it screws up the brilliant tagging-based approach in DD
This seems almost trivial to implement. You are using a config file just add the tag field since the integration is at a project level. Currently using project name and it is less than ideal and extremely inflexible.
At this time the cluster-level labels (accessible/manageable via Atlas API only, not in the UI) are not passed through to Datadog. This is definitely an interesting use case that we will explore in future.
It is possible to assign labels to a cluster as indicated in the following doc:
In our case, we are expecting having this labels propagated in datadog attached to the cluster instances..