getsentry / getsentry/sentry

Restart onError sampling for replays after stopping

Aberta
#77,458 4 comentários 0 reações 0 responsáveis Ver no GitHub
Improvement Replays
Linguagem predominante
Python
Estrelas
44.8k
Forks
4.9k
Merge médio
22h 21min
PRs com merge (30d)
586

Descrição

### 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

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Domínio
observability
Tipo de issue
Funcionalidade
Dificuldade
5/5
Tempo estimado
Mais de uma semana
Status de atividade
Estagnada
Clareza
Precisa de esclarecimento
Facilidade para iniciantes
35/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.