Restart onError sampling for replays after stopping
- 主要言語
- Python
- スター
- 44.8k
- フォーク
- 4.9k
- 平均マージ
- 22時間 21分
- マージ済み PR(30日)
- 586
説明
### Problem Statement
We received the following message from a customer:
One account in our team has multiple roles that can be switched. We hope that when the user switches roles, the errors that occur will be recorded in a new Replays.
The latest version does not have replay.setupOnce(). Simply using replay.stop() and replay.start() will not generate new Replays. I only want to use replaysOnErrorSampleRate, because if replaysSessionSampleRate or tracesSampleRate is used, replay.start() will be executed when switching users, and then a Replay without error records will be generated.
### Solution Brainstorm
Expose a public API to allow for restarting of onError sampling after replay has been stopped.
### Product Area
Replays
コントリビューションガイド
調査の方向性
Start by reviewing the replay lifecycle around replay.stop() and replay.start(), focusing on how replaysOnErrorSampleRate behaves after stopping. Define the public restart behavior so switching roles can create a new error-triggered Replay without enabling session or trace sampling. The issue names no files or tests, so those entry points must be located first.
索引モデルが issue の本文から書いたものです。
評価
- 領域
- observability
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 35/100