open-telemetry / open-telemetry/opentelemetry-android
In crashes and ANR put the state of all the threads in attributes
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 297
- Forks
- 113
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 51
Description
Expected Behavior
For events, device.anr and device.crash we should also put the state and stactrace of the all the threads present in the system. This becomes really useful in case of ANR where more than one thread participate in ANR
Current Behavior
We only put state of current thread where ANR or crash happened
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the handling of the device.anr and device.crash events, starting from where the current thread's state is added to event attributes. Determine how all present threads and their stack traces are represented, then verify that both event types include each thread's state and stack trace rather than only the triggering thread.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile-dev, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100