getsentry / getsentry/sentry-react-native
[OTEL] Support OpenTelemetry
- Lingua principale
- TypeScript
- Stelle
- 1.8k
- Fork
- 366
- Merge medio
- 1g 5h
- PR unite (30g)
- 93
Descrizione
### 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]()
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia con la SDK Develop Spec e la GitHub Discussion collegate, quindi valuta l’integrazione esistente di React Native Sentry SDK e i relativi percorsi di tracing e acquisizione degli errori. Definisci come gli span OpenTelemetry e il contesto propagato verrebbero mappati in Sentry senza interferire con le richieste del collector. Il lavoro sarà considerato completato quando sarà disponibile un piano di implementazione concordato per i requisiti documentati relativi all’elaborazione degli span, alla propagazione e al collegamento degli errori.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- react-native, typescript
- Ambito
- mobile-dev, observability
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100