getsentry / getsentry/sentry-java
Investigate newly added Android ProfilingTriggers APIs
- Dominant language
- Kotlin
- Stars
- 1.4k
- Forks
- 478
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 67
Description
Android added trigger-based profiling APIs alongside `ProfilingManager` (explicitly out of scope in [JAVA-319](https://linear.app/getsentry/issue/JAVA-319/add-new-option-to-use-profilingmanager-instead-of-old-debug-method), now Done). Investigate what trigger conditions are available and whether Sentry's profiling integration should adopt them for smarter/conditional capture (e.g. only profile on slow frames or ANR-risk situations).
Contributor guide
Research direction
Start by reviewing Android's trigger-based profiling APIs alongside ProfilingManager, then read the linked JAVA-319 context. Compare the available trigger conditions with Sentry's current profiling integration. Done means documenting which conditions are usable and whether adopting them is recommended, including the expected capture behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100