Sending Logs to Backend Before Forwarding to Datadog (Without Exposing clientToken)

[maoryadin]

I would like to implement a method to send logs to my backend first, rather than directly to Datadog.

This would allow my backend to perform checks or transformations on the payload before forwarding it to Datadog. Additionally, this setup would prevent the need to expose the clientToken on the frontend, which is essential for maintaining security.

Is this approach supported by Datadog, or are there any recommended best practices for achieving this?

Thank you!

[amortemousque]

Hello @maoryadin,
You can configure a proxy URL to send the Logs / RUM events to you backend. Here is the guide. This guide focuses on the RUM SDK but the same capability exists for the Logs SDK.

[rodgarcialima]

@maoryadin @amortemousque This is exactly what I was trying to achieve, and the proxy works fine, but my "proxy" backend requires authentication (Bearer Token), and this is not possible with the current proxy implementation. I'd love to see a way of injecting headers before the proxy call.

[amortemousque]

Hello @rodgarcialima,
Thanks for the feedback!
Currently the proxy does not support passing headers but it seems a legitimate use case. I'll bring it to the team and let you know.