-
Notifications
You must be signed in to change notification settings - Fork 518
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
Enable back pressure monitor in Potel #3602
Conversation
❌ 3005 Tests Failed:
View the top 3 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
@@ -45,6 +45,18 @@ def dropped_result(span_context): | |||
# type: (SpanContext) -> SamplingResult | |||
trace_state = span_context.trace_state.update(SENTRY_TRACE_STATE_DROPPED, "true") | |||
|
|||
# Tell Sentry why we dropped the transaction/span |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to match the logic in the earlier tracing impl, we should rather do this at the end of the transaction flow, so I'd not do this here but in span processor on_end
and only for the root span case. Here it will apply to every span and the numbers will be wrong.
If the transaction is not sampled, the |
Co-authored-by: Neel Shah <[email protected]>
This enables back pressure management in POtel.
It down samples in case of the transport not being healthy and also sends outcomes to Sentry.
Right now the sampling is done on span level, but should be done on transaction level, which is not possible right now, because we do not have a reference to the transaction (root span) in the sampler right now. This will be done in a separate PR.
The test that is updated in this PR still fails, because it needs the sample_rate to be somewhere on the Span, but this will be done in a separate PR.