Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Hey Ory team :wave:

We have been trying to upgrade our Oathkeeper version to the latest version v0.40.2.
And we are struggling with *distributed tracing between OpenTelemetry and Datadog* (since datadog has been removed as trace backend)

We were able to set up sending Oathkeeper OTEL traces to the datadog-agent, and accept them, using this doc: <https://docs.datadoghq.com/opentelemetry/otlp_ingest_in_the_agent/?tab=kuberneteshelmvaluesyaml>

However, the traces are all alone, and they are not correlated with our datadog traces from other previous and called services anymore.
Because the X-Datadog-* headers obviously don't match the standard B3 headers.

Anyone knows how to let the datadog-agent accept OTEL headers and correlated the traces? :slightly_smiling_face:

(we've created <https://help.datadoghq.com/hc/en-us/requests/1176629> on the Datadog support)

Found out by myself :slightly_smiling_face:
Feel free to ask me if you need info about this!