getsentry / getsentry/sentry-react-native
[OTEL] Support OpenTelemetry
- 主要言語
- TypeScript
- スター
- 1.8k
- フォーク
- 366
- 平均マージ
- 1日 6時間
- マージ済み PR(30日)
- 94
説明
### 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]()
コントリビューションガイド
調査の方向性
リンクされている SDK Develop Spec と GitHub Discussion から始め、既存の React Native Sentry SDK 統合と、その tracing およびエラーキャプチャの経路を評価します。OpenTelemetry の span と伝播されたコンテキストを、collector のリクエストに干渉せずに Sentry にマッピングする方法を定義します。span 処理、伝播、エラー接続に関する文書化された要件について、合意済みの実装計画ができれば完了です。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- react-native, typescript
- 領域
- mobile-dev, observability
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100