Setting the Datadog source of nginx-ingress-controller to nginx-ingress-controller

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:

image

The nginx logs do appear in Datadog, which is great - however, they come through with the source set to controller:

image

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?

Links:
Datadog service
API gateway service (with nginx logs)

Thanks for the help!

Would just like to bump this topic please; still an open question for us :slight_smile:

Hello @will ,

Sorry for the late answer but this looks like a Datadog configuration issue.

Can you give me more information on this issue?
Do you have information on what you need to modify to have the correct display name?

Regards,
Charles-Edouard

Hello @ce_gagnaire,

Thanks for the message!

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.

I have a feeling it has something to do with the helm chart config set here https://console.qovery.com/organization/ca61ed27-2145-4a0f-b7d5-cc6b70be5aa6/project/2c562530-59a5-4bc6-b48d-90fab562bdb7/environment/f21f4ef0-e944-480d-a190-e71407bfd182/application/13ada675-6fdc-41ef-94dc-8464cc4234f6/settings/values-override-file and using Labels & Annotations | Docs | Qovery (but there it says “Helm is not supported as you can directly add extra annotations within your helm chart.”) but I’m struggling to put the pieces together.

Any guidance you can offer, would be very much appreciated!

Hello @will ,

sorry for the late answer,

do you still need help on this topic?

Regards,
Charles-Edouard

Sorry for delayed reply - was away: yes please, would be very, very helpful to get this working! Thanks!

Hello @will,

no problem, I will loop with the team to see how we can help you on this topic.

Regards,
Charles-Edouard

Thank you @ce_gagnaire !

Hello @will ,

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!

Regards,
Charles-Edouard

1 Like

Hello @will ,

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?

We tried it by duplicating the already existing Nginx pipeline and changing the source to controller

Please let me know if this is helpful for you.

Regards,
Charles-Edouard

1 Like

Hello @ce_gagnaire,

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.

Thanks again!
Will

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.