-
Notifications
You must be signed in to change notification settings - Fork 497
chore(config): migrate spanTimeout #4263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(config): migrate spanTimeout #4263
Conversation
BenchmarksBenchmark execution time: 2025-12-19 17:26:25 Comparing candidate commit f74672a in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 9 metrics, 0 unstable metrics. |
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🔗 Commit SHA: f74672a | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
Codecov Report❌ Patch coverage is
Additional details and impacted files
🚀 New features to boost your workflow:
|
94067c6 to
af44c81
Compare
c24f1b3 to
3d498ae
Compare
3d498ae to
f39cc0c
Compare
af44c81 to
e8ff61c
Compare
f39cc0c to
e9e8dd2
Compare
e8ff61c to
bd2f3c0
Compare
bd2f3c0 to
f74672a
Compare
e9e8dd2 to
c8b32da
Compare

What does this PR do?
Migrate tracer to use Config.spanTimeout. Also, change spanTimeout true default from 0 to 10 minutes. This was always the effective default, although only set if debugAbandonedSpans was enabled. With this change, the default is consistent, but the feature remains unused if debugAbandonedSpans is not enabled.
Motivation
https://datadoghq.atlassian.net/browse/APMAPI-1748
Reviewer's Checklist
./scripts/lint.shlocally.Unsure? Have a question? Request a review!