Datadog-agent: Kubernetes event collector does not respect additional tags configured for dd-agent

[izakp]

Describe what happened:
The Kubernetes event collector does not append additional tags configured for the agent at runtime (as does, for example the Docker integration).

Describe what you expected:
I expected to see Kubernetes events tagged with the tags we configured on the agents running in our Kubernetes cluster. We configure the agent to append the tags env:staging / env:production (depending on which cluster it is deployed to) in order to differentiate / filter between event / metric streams and Kubernetes events are not tagged as such.

Steps to reproduce the issue:
Install the Datadog agent on a Kubernetes cluster, enable event collection and inspect event tags.

Additional environment details (Operating System, Cloud provider, etc):
Running Kubernetes 1.6.3 on AWS via Kops

[CharlyF]

Hello @izakp,
Thank you for opening this!
Indeed, the tags from the Datadog configuration file or via the environment variables are not added to the events.
I have added a card to our backlog so it can be fixed.
Apologies for the headache.

In the meantime, a workaround would be to add the tags to the kubernetes_apiserver.yaml located at /etc/datadog-agent/conf.d/kubernetes_apiserver.d/conf.yaml in the pod.
You can find an example here:
https://github.com/DataDog/datadog-agent/blob/master/Dockerfiles/cluster-agent/conf.d/kubernetes_apiserver.d/conf.yaml.default

Let me know if that helps.

[izakp]

@CharlyF thanks for the quick reply! And perfect - that is exactly what I was looking for.

[kalymero]

hi @CharlyF
i have the same issue for custom events sent to the DogStatsD server and in my case the workaround you propose does not really work.

Do you have an ETA for releasing the fix?

Thanks

[tehlers320]

Can this be re-opened please? This bug is 3 years old and im fairly certain it still applies. Or link to the PR that corrected the issue. Thanks.

[CharlyF]

Hi @tehlers320 - Happy to re-open, I increased the priority of this feature for the next version of the Cluster Agent.
Thanks.
.C