getsentry / getsentry/sentry-react-native
[OTEL] Support OpenTelemetry
- Lenguaje dominante
- TypeScript
- Estrellas
- 1.8k
- Forks
- 366
- Merge medio
- 1 d 6 h
- PR fusionados (30 d)
- 94
Descripción
### 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]()
Guía de contribución
Línea de trabajo
Comienza con la SDK Develop Spec y la GitHub Discussion enlazadas; después, evalúa la integración existente de React Native Sentry SDK y sus rutas de tracing y captura de errores. Define cómo se mapearían los spans de OpenTelemetry y el contexto propagado a Sentry sin interferir con las solicitudes del collector. Se considerará terminado cuando exista un plan de implementación acordado para los requisitos documentados de procesamiento de spans, propagación y conexión de errores.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- react-native, typescript
- Área
- mobile-dev, observability
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100