-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
feat(server): Ingest and normalize sample rates #910
Conversation
cc @lobsterkatie please double-check the test and the schema. |
* master: fix(server): Normalize user reports during ingestion (#903)
33c7250
to
625d2d0
Compare
Looks good. Do the other possible values for the method ('explicitly_set' and 'inheritance') just get ignored for the moment? (Which is fine - just want to make sure they don't break things.) |
@lobsterkatie not sure if I understand correctly, do you mean if we accept other values for "id"? The identifier can be any value because is defined as string like this: id: Annotated<String> |
Yup, that was my question, thanks. We're good. |
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.
JS parts look good!
* master: fix: Build proper 64-bit Linux wheel release: 0.8.2 chore: Switch to manylinux2010 (#917) meta(py): Changelog for 0.8.2 ci: Add an action to release the library (#916) ref: Remove Compatibility mode for Session Aggregates (#913) release: 21.1.0 ci: Fix clippy command invocation ci: Run clippy via the cargo action feat(server): Ingest and normalize sample rates (#910)
We want to be able to look at the sample rate users set for specific events and
transactions. In regular mode, Relay takes the sample rates from the effective
event item and forwards them to the upstream. In processing mode, the sample
rates are instead written into
_metrics
.The JavaScript SDK implements this with getsentry/sentry-javascript#3068.