-
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
ref(metrics): Aggregate metrics before rate limiting #3746
Conversation
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.
Q: what's the behavior if the project config isn't fetched, do we keep aggregating metrics indefinitely?
Yes. |
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.
LGTM.
In the future, there should be a limit on the number of metrics Relay accepts if a project config can't be fetched.
* master: chore(dynamic-sampling): Remove metrics for dsc tracking (#3766) feat(web-vitals): add support for mobile browsers (#3762) feat(profiles): Support profiler_id in context (#3714) ref(normalization): Add origin and event_type tags to normalization decision (#3764) feat(rate-limiting): Add back docs with examples on rate limiting (#3761) feat(spans): Correctly emit negative outcomes for rate limited transactions that have nested spans (#3749) ref(metrics): Remove unused sentry extra data (#3758) feat(statsd): Emit tokio runtime metrics via statsd (#3755) ref(metrics): Aggregate metrics before rate limiting (#3746) ref(cogs): Remove unused metric, revert to released usage accountant (#3756) build(cargo): Update curve25519-dalek from 4.0.0 to 4.1.3 (#3745) test(deps): Bump requests from 2.31.0 to 2.32.2 (#3752)
Implements the rest of #3662.
Fixes #3553.
Removes all pre-aggregation and rate limit steps before we receive a project state, all rate limiting is done after aggregation.