Fix span enrichment singleton initialization - #12273
gh-worker-dd-mergequeue-cf854d[bot] merged 3 commits into
Conversation
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
|
🎯 Code Coverage (details) 🔗 Commit SHA: 3fea523 | Docs | View more details | Give us feedback! |
There was a problem hiding this comment.
More details
The lazy holder creates the singleton after its production dependencies and keeps the same process-wide writer across restarts.
🤖 Datadog Autotest · Commit 3fea523 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
leoromanovsky
left a comment
There was a problem hiding this comment.
Thanks for finding and resolving this. What made it missed in system tests?
The regression test for this already exists: So that needs to be updated |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What Does This Do
Motivation
Feature-flag evaluations succeed, but span enrichment silently fails because the eager singleton captures null dependencies during static initialization. The failure is visible in debug logs as:
Consequently, span-enrichment events were dropped, and traces were emitted without the expected feature-flag tags.
Additional Notes
Contributor Checklist
Jira ticket: FFL-3090