-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
ref(replays): Add option which disables publishing to Snuba from Relay #98353
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
Changes from all commits
e2b7486
794e9f4
7b9b68c
c7bf1e5
b170705
3e7410c
7b489f0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -42,6 +42,7 @@ def inner(version, global_): | |
| "profiling.profile_metrics.unsampled_profiles.sample_rate": 1.0, | ||
| "relay.span-usage-metric": True, | ||
| "relay.cardinality-limiter.mode": "passive", | ||
| "replay.relay-snuba-publishing-disabled": True, | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: New Option Not Recognized in Config NormalizationThe new |
||
| "relay.metric-bucket-distribution-encodings": { | ||
| "custom": "array", | ||
| "metric_stats": "array", | ||
|
|
||
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.
Potential bug: The feature to publish replay events to Snuba is non-functional due to a key mismatch. The code looks for
relay_snuba_publish_disabled, but the option is named differently.Description: There is a mismatch between the configuration option name
replay.relay-snuba-publishing-disabledand the key the consumer code attempts to retrieve from the recording payload,relay_snuba_publish_disabled. Becauserecording.get("relay_snuba_publish_disabled")insrc/sentry/replays/consumers/recording.pywill always returnNone, theshould_publish_replay_eventcontext value is alwaysNone. This causes the conditional check insrc/sentry/replays/usecases/ingest/__init__.pyto always evaluate to false. As a consequence, thepublish_replay_eventfunction is never called, rendering the feature to publish replay events to Snuba completely non-functional regardless of its configuration.Suggested fix: Correct the key used in
src/sentry/replays/consumers/recording.pyfromrelay_snuba_publish_disabledto match the key sent by Relay. Additionally, since the flag name implies disabling publishing, the conditional logic insrc/sentry/replays/usecases/ingest/__init__.pymay need to be inverted to correctly handle the flag's intent.severity: 0.8, confidence: 0.95
Did we get this right? 👍 / 👎 to inform future reviews.