Support baggage propagation without enabling tracing#11624
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4749235a1c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
👋 Hey @aviramha! Thanks for the contribution. Feature requests are routed through customer support channels - if you could leave a request there, we can make sure it gets reviewed by the proper team. 🙇♂️ |
|
We're not a customer - where are the support channels? |
|
Feel free to open a ticket or join the public Slack here. |
|
Which channel would be relevant? |
|
👋 I consulted internally and the best course of action is to have your customers who would like this feature to open a ticket with our support team! |
What Does This Do
Enable DataDog customers' use the built in context propagation without needing to enable APM using env
DD_PROPAGATE_CONTEXT=trueMotivation
We have customers that want to propagate context to use our product. When customers are users of OTEL libraries they can just enable that feature, but customers of DataDog are blocked in either needing to:
This allows them to stay within DD ecosystem and being on par with other auto instrumentation o11y libraries.
Additional Notes
Contributor Checklist
Docs PR
Labels - seems I can't do it from my side?