Hey folks, is it still possible to use Datadog as ...
# ory-selfhosting
a
Hey folks, is it still possible to use Datadog as tracing backend for Kratos with Helm Chart version `0.24.5`/`0.25.0` ? I've upgraded from
0.23.0
and it complains that only
zipkin
or
jaeger
are supported now.
Copy code
The configuration contains values or keys which are invalid:
tracing: map[provider:datadog]
         ^-- doesn't validate with "<ory://tracing-config#>"

The configuration contains values or keys which are invalid:
tracing.provider: datadog
                  ^-- value must be one of "jaeger", "zipkin"

time=2022-08-16T11:16:51Z level=fatal msg=Unable to instantiate configuration. audience=application error=map[message:I[#/tracing] S[#/properties/tracing/$ref] doesn't validate with "<ory://tracing-config#>"
  I[#/tracing/provider] S[#/properties/provider/enum] value must be one of "jaeger", "zipkin"] service_name=Ory Kratos service_version=v0.10.1
This is the message now šŸ˜•
p
@worried-kitchen-94392
šŸ™Œ 1
a
I have also tried configuring via env vars, as suggested in https://www.ory.sh/docs/kratos/reference/configuration, with no luck
w
This is not helm dependent, but on the version of kratos, the app itself is complaining. @high-optician-2097 did we depreciate datadog in kratos? Did you check the docs/release notes for changes?
a
Thanks @worried-kitchen-94392, the release notes indeed mention that Datadog support is dropped.
h
yeah, we dropped it because of open telemetry. once an easy exporter is available we can readd it (PRs welcomed šŸ™‚ )
a
https://github.com/ory/x/pull/582 I've created this, in order to support exporting tracing data to an agnostic OTEL exporter.
(please lemme know if it makes sense :D)
I see the PR was approved by @icyphox on Github. Can we get it merged? I would love to be able to get traces from kratos again šŸ™‚ (in this case, via a opentelemtry exporter) The way I envision this to land as a change in the helm chart is: • Get https://github.com/ory/x/pull/582 merged • create a release of Ory/X. • Upgrade ory/x dependency in Kratos to the new version. • create a release of Ory/Kratos • Upgrade ory/kratos dependency in Ory/k8s to the new version • create a release of ory/k8s I'm happy to do all this, but am unsure of how all these processes work (or if I'll have permissions to do them). Can anybody provide some guidance here?
Bumping this, hopefully someone can help with the merge?
h
ty, done
a
Thank you @high-optician-2097! I'll create a PR to Kratos updating the ory/x version then :)