getsentry / getsentry/sentry-react-native
[OTEL] Support OpenTelemetry
- Vorherrschende Sprache
- TypeScript
- Sterne
- 1.8k
- Forks
- 366
- Ø Merge
- 1 T. 5 Std.
- Gemergte PRs (30 T.)
- 93
Beschreibung
### Description
OpenTelemetry is a popular open standard for collecting observability data. It has grown in popularity across many during programming languages and vendors in recent years. There is a growing interest to have support in react native. There is work to extend Sentry SDK support for OpenTelemetry in Sentry.
We should assess the existing potential of instrumenting with OpenTelemetry and Sentry SDKs in react native application to send this data to Sentry, and properly integrate it with the existing functionality of Sentry and its SDKs.
### High level requirements
* OpenTelemetry SDK responsible for capturing spans and propagated traces
* Sentry SDK responsible for converting those spans into sentry spans and transactions
* to be sent to Sentry and not interfere with any existing OTEL collector requests
* Sentry SDK takes care to ensure tracing is connected with errors
* Sentry SDK remains responsible capturing errors and all other features of Sentry which OpenTelemetry SDKs cannot support
Full details of the implementation is being continuously documented the [SDK Develop Spec]()
### Details
* span processor - transforming OTEL spans into Sentry spans within Sentry transactions
* span name and description
* parent child relationships
* trace/context propagator - including DSC and trace context
* [https://opentelemetry.io/docs/reference/specification/context/api-propagators/]()
## Reference
GH Discussion: [https://github.com/getsentry/sentry/discussions/40712]()
Beitragsleitfaden
Rechercherichtung
Beginne mit der verlinkten SDK Develop Spec und GitHub Discussion und bewerte anschließend die bestehende React Native Sentry SDK-Integration sowie deren Tracing- und Fehlererfassungspfade. Lege fest, wie OpenTelemetry-Spans und propagierter Kontext in Sentry abgebildet werden, ohne Collector-Anfragen zu beeinträchtigen. Als erledigt gilt die Aufgabe, wenn für die dokumentierten Anforderungen an Span-Verarbeitung, Propagation und Fehlerverknüpfung ein abgestimmter Implementierungsplan vorliegt.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- react-native, typescript
- Bereich
- mobile-dev, observability
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100