open-telemetry / open-telemetry/opentelemetry-android
Track low memory events
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 297
- Forks
- 113
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 51
Description
Android's ComponentCallback2 interface allows for the app to listen for OS-level memory events that tell the app the process is trying to recover memory. Surfacing these warnings/alerts (as Events?) could be useful as it could be an indication the app is running low on resources so performance could be hampered.
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
Start by reading Android's ComponentCallback2 documentation and the repository's existing event APIs; the issue does not name a file, test, or entry point. Determine how low-memory callbacks should be represented as telemetry and what event fields and delivery behavior are expected. Done means the agreed warnings or alerts are surfaced consistently with existing instrumentation and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100