-
Notifications
You must be signed in to change notification settings - Fork 93
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
feat(server): Add support for breakdowns ingestion #934
Conversation
7af00e6
to
05f7067
Compare
05f7067
to
ad5f422
Compare
@untitaker @jan-auer A heads up, I've updated the |
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.
Alright, this looks good. A number of suggestions below, and then going for the final review pass.
Co-authored-by: Jan Michael Auer <[email protected]>
transaction_item = generate_transaction_item() | ||
transaction_item.update( | ||
{ | ||
"breakdowns": {"span_ops": {"lcp": {"value": 202.1},}}, |
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.
Why are you setting this above just to override it here?
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.
@k-fish Unsure what you mean. Events might arrive to Relay with breakdown values; this test is to demonstrate that breakdown objects are recursively merged instead of overwritten.
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.
Ahhh I see. I didn't know the intent was to test the recursive merge. That makes sense then 👍
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.
Thank you, @dashed!
impl Breakdowns { | ||
pub fn is_valid_breakdown_name(name: &str) -> bool { | ||
name.chars() | ||
.all(|c| matches!(c, 'a'..='z' | 'A'..='Z' | '0'..='9' | '-' | '_' | '.')) |
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.
Note that this doesn't require the first character to be a letter, which would be a usual requirement.
Co-authored-by: Jan Michael Auer <[email protected]>
* master: fix(server): Remove dependent items from envelope when dropping transaction item (#960) fix(clippy): Fix clippy 1.51.0 warnings (#965) feat(server): Add support for breakdowns ingestion (#934) build: Update schemars and remove workarounds (#961) feat(server): Add rule id to outcomes coming from transaction sampling (#953)
Reference: https://getsentry.atlassian.net/browse/VIS-617
Breakdowns are product-defined numbers that are indirectly reported by the client, and are materialized during ingestion. (credit to @jan-auer for this definition)
This PR contains the following changes:
breakdowns
as a top-level optional field to the event schema.TODO
http
,db
,browser
,resource
(useString:: starts_with()
)breakdowns
event field