-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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(eap-spans): Add feature to control span ingestion in EAP #80064
chore(eap-spans): Add feature to control span ingestion in EAP #80064
Conversation
@@ -65,6 +65,7 @@ | |||
"projects:span-metrics-extraction", | |||
"projects:span-metrics-extraction-addons", | |||
"organizations:indexed-spans-extraction", | |||
"organizations:ingest-spans-in-eap", |
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.
Does this flag need to be exposed to relay?
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.
Yes, I'm making a PR to Relay too so we can add a field to the span payload to let the Snuba EAP consumers know they should ingest the span or not.
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #80064 +/- ##
==========================================
- Coverage 78.12% 78.11% -0.02%
==========================================
Files 7163 7159 -4
Lines 316700 316612 -88
Branches 43663 43646 -17
==========================================
- Hits 247414 247310 -104
- Misses 62944 62954 +10
- Partials 6342 6348 +6 |
Plan is to then tag each span with a field instructing the consumer to either ingest or discard.
getsentry/snuba#6486
getsentry/relay#4206