Skip to content
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(outcomes): Aggregate more outcomes [INGEST-671] #1134

Merged
merged 5 commits into from
Nov 24, 2021

Conversation

jjbayer
Copy link
Member

@jjbayer jjbayer commented Nov 23, 2021

Erase event_id and remote_addr from the following outcomes, so that they can be efficiently aggregated.

  • RateLimited(_): the biggest offenders are usage_exceeded and abuse, and in both cases we don't need outcomes to debug individual events.
  • Invalid(ProjectId): this is easy to diagnose from other info and usually applies to all traffic, not individual events.
  • FilteredSampling(_): is expected to create too much load when high-cardinality fields are preserved.

@jjbayer jjbayer requested review from a team, untitaker, jan-auer and mitsuhiko November 23, 2021 13:45
@jjbayer jjbayer merged commit 2a82bff into master Nov 24, 2021
@jjbayer jjbayer deleted the feat/aggregate-more-outcomes branch November 24, 2021 08:51
jan-auer added a commit that referenced this pull request Nov 24, 2021
* master:
  test(outcomes): Fix sort order in flaky test (#1135)
  feat(outcomes): Aggregate more outcomes (#1134)
  ref(outcomes): Fold processing vs non-processing into single actor (#1133)
  build: Update symbolic to support UE5 (#1132)
  feat(metrics): Extract measurement ratings, port from frontend (#1130)
  feat(metrics): Another statsd metric to measure bucket duplication (#1128)
  feat(outcomes): Emit outcomes as client reports (#1119)
  fix: Move changelog line to right version (#1129)
  fix(dangerjs): Do not suggest to add JIRA ticket to changelog (#1125)
  feat(metrics): Tag metrics by transaction name [INGEST-542] (#1126)
jjbayer added a commit that referenced this pull request Mar 26, 2024
#1134 introduced aggregation for
most outcomes, but it did not include inbound filters.

Outcomes are no longer used for investigating individual events, so we
might as well save resources by aggregating all outcomes
unconditionally.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants