getsentry / getsentry/sentry

Restart onError sampling for replays after stopping

Aperta
#77,458 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Improvement Replays
Lingua principale
Python
Stelle
44.8k
Fork
4.9k
Merge medio
22h 21m
PR unite (30g)
586

Descrizione

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

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Ambito
observability
Tipo di issue
Funzionalità
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
35/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.