relay
relay copied to clipboard
getsentry
Sentry event forwarding and ingestion service.
See context here: https://linear.app/getsentry/issue/LOGS-104 The OTEL protocol requires nanosecond precision, which we support in EAP. Right now the SDKs send timestamps in microsecond precision (as defined in the `Timestamp` struct):...
Currently the `Getter` trait requires a bunch of manual boilerplate, we should be able to auto generate all of it using our existing derive macros, or at least make the...
For sentry.io production infrastructure we plan to have some envoy route matching based on additional header. Allow to configure arbitrary headers passed to upstreams.
Once we have Span and SpanV2 envelopes accepted, we should review envelope limits, they might already be fine, we should start strict, we can always be more lenient in the...
When users host Relay on-premises they want to restrict ingestion only through that local self-hosted Relay: * Add option to Sentry to restrict ingestion bypassing local Relay * The path...
The Unity SDK (`sentry.dotnet.unity`) when not aware of which platform it's running on, which is the case for consoles when using our open source SDK. Reports the raw OS name...
Now since the serialization format and schema may change in the future, we need to stay forward compatible. A customer should not have to upgrade an older Relay when we...
Based on https://github.com/getsentry/sentry-docs/pull/13203, let's wait for this to be merged so details are settled. We want to add a new `page` context, based on the develop docs schema: ```json {...
This is something I stumbled upon while working on this PR (worth reading for context): https://github.com/getsentry/sentry/pull/88539 Only, when both frontend and backend are involved in an issue, the client OS...
