feat: Enable tracing

[ptescher]

Proposed changes

Enable tracing via ory/x/tracing just like Hydra etc.

Checklist

• I have read the contributing guidelines
• I have read the security policy
• I confirm that this pull request does not address a security vulnerability. If this pull request addresses a security
  vulnerability, I confirm that I got green light (please contact [email protected]) from the maintainers to push the changes.
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation within the code base (if appropriate)
• I have documented my changes in the developer guide (if appropriate)

[aeneasr]

Cool! Could you maybe add a jaeger example to the docker compose file similar to the way we have done it for Hydra (see code)? That would be super helpful to check out the feature!

[ptescher]

@aeneasr done!

[ptescher]

[aeneasr]

Awesome, thank you!

[snikch]

FYI this capability isn't in the docs so it was a nice surprise to find this PR!

Confirming though, this doesn't add the spans to outgoing requests from Oathkeeper does it? i.e. it won't allow be to continue tracing through to Hydra.

[daviddelucca]

@snikch does it work? I have set jaeger but I don't see oathkeeper requests to upstream or mutator

[snikch]

@daviddelucca works fine for us

[daviddelucca]

@snikch

I'm just seeing request for introspection. Are you able to find tracing for upstream host requests?

[snikch]

@daviddelucca ah yes, correct. I added this separately here: #640

You'd need to have the equivalent code added to other endpoints I think. A bigger refactor would be to use a shared http client with tracing enabled so each separate area doesn't need to have it implemented.