-
Notifications
You must be signed in to change notification settings - Fork 492
chore(config): migrate tracer.profilerHotspots #4216
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
base: main
Are you sure you want to change the base?
Conversation
BenchmarksBenchmark execution time: 2025-12-09 16:56:42 Comparing candidate commit 7ec2f1e in PR branch Found 0 performance improvements and 3 performance regressions! Performance is the same for 6 metrics, 0 unstable metrics. scenario:BenchmarkSingleSpanRetention/no-rules-25
scenario:BenchmarkSingleSpanRetention/with-rules/match-all-25
scenario:BenchmarkSingleSpanRetention/with-rules/match-half-25
|
Codecov Report❌ Patch coverage is
Additional details and impacted files
🚀 New features to boost your workflow:
|
What does this PR do?
Tracer migrates to using Config.profilerHotspots instead of its own config.profilerHotspots.
Motivation
datadoghq.atlassian.net/browse/APMAPI-1748
Reviewer's Checklist
./scripts/lint.shlocally.Unsure? Have a question? Request a review!