We followed this guide to setup Datadog (with some adjustments to only enable logging).
We also enabled logging for nginx-ingress-controller after seeing it referenced here:
The nginx logs do appear in Datadog, which is great - however, they come through with the source set to controller:
We would like them to instead come through with the source matching the integration name: nginx-ingress-controller (the integration name from the Datadog docs) to benefit from the Datadog’s automatic setup for integrations.
How do we set the source of nginx-ingress-controller to nginx-ingress-controller?
From what I can follow, Datadog says here: Kubernetes log collection that I should be able to some how set a Pod label like tags.datadoghq.com/service: "<SERVICE>"
In our specific case, I believe setting this to nginx-ingress-controller (the name of the Datadog integration) will lead to Datadog auto formatting the nginx logs for us.
If possible, I’m looking for a way to add this pod label in Qovery.
We’ve been quite busy this week, but we’re actively working on finding a solution for you. I’ll have more information to share by this Friday and will keep you updated.
I am looking forward to getting this resolved for you soon!
I reviewed your problem with the team and I have some information for you.
It is not possible to add labels on the Nginx Ingress.
From what I understand of your problem, I don’t think you can add this label in the Datadog Helm Chart configuration, but maybe you can ask Datadog support on this topic?
In Datadog, you have the possibility to add Pipelines. Can this be a solution for you?
Thank you very much for looking into it! Thanks for the pipeline option - we manually added it as a workaround, and were hoping to get the automatic-integration pipeline detection based on source instead. So will stick to the manual pipeline workaround for now.
