chore: deprecate datadog tracer + update docs#11643
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
| tracing.enable_tracing(DatadogTracer(tracer)) | ||
| ``` | ||
| :::info | ||
| Check out the [integration page](https://haystack.deepset.ai/integrations/datadog) for more details and example usage. |
There was a problem hiding this comment.
I'd say that in general the integration page is just a showcase but our docs should be the source of truth, so I'd not point users to the integration page.
I'd update this section and/or create a new page for the component.
There was a problem hiding this comment.
That's fair but should we do that in a follow up PR? This is following the same format as is done for our other tracers in this page where we just link to the integration page and only for mlflow do we show a small amount of code set up.
There was a problem hiding this comment.
And you're right we already document our connector components sorry for missing that. Adding the datadog connector docs to this PR
There was a problem hiding this comment.
@anakin87 could I get one more review on the new connectors page I added?
Related Issues
Proposed Changes:
deprecate usage of DatadogTracer in Haystack core and point users to new integration
How did you test it?
added new unit test
Notes for the reviewer
Waiting for release of new integration
datadog-haystackbefore mergingChecklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:and added!in case the PR includes breaking changes.