getsentry / getsentry/sentry

Restart onError sampling for replays after stopping

未关闭
#77,458 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
Improvement Replays
主要语言
Python
星标
44.8k
派生
4.9k
平均合并
22 小时 21 分钟
30 天内合并 PR
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
预计耗时
一周以上
活跃度
停滞
描述清晰度
需要澄清
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。