Hi have a question regarding tracing in keto, I deployed a self hosted oathkeeper + keto + kratos, and i connected all to Datadog, unfortunately i see tracing only for oathkeeper and kratos, is there a problem with keto tracing? I've managed to connect all service to DD and i get a log from keto as follows:

2022/09/15 10:09:40 Datadog Tracer v1.33.0 INFO: DATADOG TRACER CONFIGURATION {"date":"2022-09-15T10:09:40Z","os_name":"Linux (Unknown Distribution)","os_version":"unknown","version":"v1.33.0","lang":"Go","lang_version":"go1.17.6","env":"","service":"ORY Keto","agent_url":"<http://10.0.1.54:8126/v0.4/traces>","agent_error":"","debug":false,"analytics_enabled":false,"sample_rate":"NaN","sampling_rules":null,"sampling_rules_error":"","tags":{"runtime-id":"84751f2b-e8d0-4425-8eab-8fd12c07fd1b"},"runtime_metrics_enabled":false,"health_metrics_enabled":false,"dd_version":"","architecture":"amd64","global_service":"ORY Keto","lambda_mode":"false","agent_features":{"DropP0s":false,"V05":false,"Stats":false}}

Can you share how you got it to work with kratos and oathkeeper? I tried to enable jaeger/zipkin a while back without any luck. 🙂

Sure! First of all I have upgraded to recent versions, and in each config I've set the config as such:

tracing:
  provider: datadog

Finally in the running container I have set the

DD_AGENT_HOST

env variable to point into the running trace agent

since

v0.9.0-alpha.0

Keto uses the same code for tracing as the other projects, so should be exactly the same steps

I can't get zipkin to work, tried Kratos

https://github.com/ory/x/pull/500 this is basically the feature, maybe you can figure out with the code what is not working for you

@steep-lamp-91158 i revived another thread, maybe you can have a look or let us know what else you need?

hmm... got it, thanks. but from the release notes i think it's not safe to upgrade to that version: v0.9.0-alpha.0 Pre-release ⚠️ Important Notice ⚠️ Due to a bug in the migrations, this version should be skipped. Greed-field deployments are not affected, but migrating to this release from previous versions might result in data loss! For details, head over to #997.

yeah sorry, that is fixed on master but we had some issues and could not release it yet