relay icon indicating copy to clipboard operation
relay copied to clipboard

Sentry event forwarding and ingestion service.

Results 203 relay issues
Sort by recently updated
recently updated
newest added

Reduces the code duplication, now also means, there is no need to keep 2 separate implementations in sync. The common denominator between the two code paths was the `EnvelopeSummary`, which...

skip-changelog

Sessions currently run through the rate limiting code, but the moment they are converted to metrics they are no longer considered for rate limiting. This is not an issue as...

Fixes an `integer out of range` error in the `times_seen` column of `sentry_groupedmessage`. This error occurs when client SDKs send events with extremely low `sample_rate` values. The Sentry backend calculates...

### Problem Statement Relay scrubs domain addresses like `my.app.service.com` to something like `*.service.com`. This is okay for a lot of cases, but for _some_ users, subdomains are meaningful to more...

enhancement

Prefixing `!` before a pattern will negate the pattern that follows. This is designed for use within inbound-filters (specifically release filters) where a customer wants to define an allow-list (as...

See also: #5156 Instead of defining pii is `true`, `maybe` or `false`, we want to be able to determine which rules are applied on a field by field basis. Now...

Currently the way PII scrubbing is configured is split into 3 modes: `true`, `maybe`, `false`. Where false never runs PII scrubbing, `maybe` only if the user specifically opted into it...

Often tokens are identifiable, because they have their unique prefix or other unique properties that identify them. We can take a look at how Secret Scanners identify secrets and implement...

``` Fixes `InitializationError: Error getting github enterprise integration config` caused by a silo boundary violation. Previously, the `SeerRpcServiceEndpoint` (running in REGION silo mode) attempted to directly access the CONTROL-plane `Integration`...

Lenient ignores all validations, but when the quantity differences are known, we should use `modify_by` instead to validate stronger.