-
Notifications
You must be signed in to change notification settings - Fork 449
chore(tracer): enhanced debug logging for sampling and span processing #14137
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
Conversation
|
Bootstrap import analysisComparison of import times between this PR and base. SummaryThe average import time from this PR is: 283 ± 4 ms. The average import time from base is: 283 ± 3 ms. The import time difference between this PR and base is: 0.3 ± 0.2 ms. The difference is not statistically significant (z = 1.57). Import time breakdownThe following import paths have shrunk:
|
Performance SLOsCandidate: munir/improve-sampling-debug-logs-2 (84fdcdd) 🔵 No Baseline Data (24 suites)🔵 coreapiscenario - 12/12 (2 unstable)🔵 No baseline data available for this suite
|
fbf4315
to
0bc0776
Compare
Blocked by: #14146 |
5a89bf9
to
2556691
Compare
0e35702
to
ed589e4
Compare
ed589e4
to
dc05ffb
Compare
2b6877f
to
5d688ed
Compare
5e2c78b
to
62dbb01
Compare
ed0bb56
to
2049d61
Compare
Motivation
Debugging trace sampling and span processing issues in production is challenging due to limited visibility into the tracer's internal decisions. Users struggle to understand why spans are dropped, which sampling rules are applied, and whether traces are being processed correctly.
Description
This PR adds comprehensive debug logging throughout the trace pipeline, providing detailed observability into sampling decisions, span lifecycle, span encoding, and span transmission to the agent. The logging is designed to be informative when debug logging is enabled.
Changes
Sampling Transparency
Span Lifecycle Visibility
Trace submissions Insights
Checklist
Reviewer Checklist