getsentry / getsentry/sentry-java
Reevaluate traceId generation places
Abierto
Java
Task
Traces
- Lenguaje dominante
- Kotlin
- Estrellas
- 1.4k
- Forks
- 478
- Merge medio
- 2 d 23 h
- PR fusionados (30 d)
- 67
Descripción
### Description
There is an "issue" with ANRs [not having the same traceId]() of the currently running transaction, if the transaction finishes right before the ANR occurs.
This is due to our TWP implementation. Should we change it?
It would mean to either
* understand if an anr is likely going to occur and don't overwrite the stored traceId when the current span finishes
* replace the traceId stored from spans only after at least 5 seconds, ensuring that the traceId stored in the `PersistingScopeObserver` is used only by ANRs
Guía de contribución
Evaluación
Este issue todavía no se ha evaluado.