feat: add resource name for Haystack Component Datadog spans

[lan666as]

Related Issues

• resolves Datadog Tracer: Set Resource Name from Component Type/Name #9333

Proposed Changes:

Set Datadog span resource name as component name and type instead of the operation name (i.e., haystack.component.run)

How did you test it?

• Unit test
• Manual verification at Datadog APM

Before

After

Notes for the reviewer

-

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[CLAassistant]

All committers have signed the CLA.

[sjrl]

@lan666as thanks for the work on this! We will be able to give this a review once you are able to add tests and mark the PR as ready.

[coveralls]

Pull Request Test Coverage Report for Build 15728163096

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.009%) to 90.154%

---

Files with Coverage Reduction	New Missed Lines	%
tracing/datadog.py	2	96.0%

Totals
Change from base Build 15727603018:	0.009%
Covered Lines:	11564
Relevant Lines:	12827

---

💛 - Coveralls

[lan666as]

Hi @sjrl, it seems the changes needed for our requirements are more extensive than anticipated. I've decided to fork the class to implement these independently and will be closing this PR. Thanks!

[sjrl]

@lan666as looking good! Could you also update tests in haystack/tracing/datadog.py to unit test this as well? I think just updating test_opentelemetry_tracer inside of the class TestDatadogTracer would be enough to test that resource name is also set in the trace.

[lan666as]

Let me resolve the CI issue first

[sjrl]

@lan666as don't worry about the formatting CI that will be resolved with this PR #9528

But if you could add a release note that would be great! Instructions for adding a release note can be found here

[sjrl]

Looks good!