relay
relay copied to clipboard
getsentry
Sentry event forwarding and ingestion service.
### Problem Statement With AWS moving to charging users for all IPv4 addresses (EIPs), not just unused EIPs, extremely-large and extremely-small customers are being financially incentivised to move to IPv6-only...
We should split the Regex pools into multiple pools, one per usecase: - Project Config - Cardinality - Quotas - Misc (metric meta) The configuration should accept the config we...
Follow-up after: #3829 We can now switch the pool for project configs to an async pool and client and instead of a lot of `spawn_blocking` calls in an async context...
> Written in collaboration with @loewenheim ## Goal The goal of this pull-request is to remove `relay_cabi`, `relay_ffi` and `relay_ffi_macros` and replace it with a more modern approach: pyo3. The...
After #3662 - Update billing consumer to *not* emit accepted outcomes for transaction metrics with the `sampled: true` tag - Update transaction consumer to *not only* emit accepted outcomes for...
Once we can read COGS data from our statsd metrics, there is no longer a need to emit the metrics to Kafka and we can remove the dependeny.
We do not generate any outcomes for dropped buckets: https://github.com/getsentry/relay/blob/4cb923f0667da94801039ff2cbd99635221dd97b/relay-metrics/src/aggregation.rs#L2006-L2009 Not sure if it even makes sense to submit outcomes at the point where the metrics aggregator shuts down, because...
It is unconditionally enabled in getsentry, we should remove the feature flag.