digidem / digidem/comapeo-core-react-native
Sentry integration: remaining work (tracking)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 8h 24m
- Merged PRs (30d)
- 9
Description
Tracking issue for completing the Sentry integration. The detailed spec lives in docs/sentry-integration-plan.md; this issue regroups the remaining plan phases into ordered workblocks, one sub-issue each. Sub-issues cite the plan sections they implement, so the plan doc stays the spec and this issue tree is the tracker.
Workblocks
| Workblock | Issue | Plan sections | Depends on |
|---|---|---|---|
| 1. Toggle rework + device classification | #75 | §11.1, §11.5, §11.6 (plumbing), §11.7 | — |
| 2. Metrics layer + debug-gated RPC tracing | #76 | §11.2, §11.3, §11.8 | #75 |
| 3. PII scrubbers (events + breadcrumbs) | #77 | §9b.1, §9b.5, Phase 5 (before_send wiring) |
— |
4. Installation-UUID user.id + rotation |
#78 | §9b.2, §11.4, §9b.9 | #75 |
| 5. Trim device detail per privacy tier | #79 | §9b.3, §9b.4, §9b.6 | — |
| 6. Usage-tier captures | #80 | Phase 5 (remainder), §11.4 | #75, #77 |
7. Verify @comapeo/core OpenTelemetry forwarding |
#81 | Phase 4 | blocked on comapeo-core#1051; most useful with #75's debug toggle |
| 8. Dashboards, alerts, volume tuning | #82 | §11.9, §11.2.c, Phase 8 | #76 in internal builds |
| 9. iOS killed-in-background heuristic (optional) | #83 | Phase 7b | — |
Suggested sequence
#75 → #76 unblocks everything metrics-related and is the highest-value path. #77 and #79 are independent and can run in parallel with it. #78 and #80 follow their dependencies. #81 waits on the upstream PR; #82 needs real data from internal builds; #83 is optional and can be picked up any time.
Phase numbering from the plan doc is kept in every sub-issue so cross-references in git history stay valid.
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 with docs/sentry-integration-plan.md, then read the linked workblocks #75–#83 and their cited plan sections. Use the dependency order in this issue to identify an available sub-issue; the tracking issue is complete when all remaining workblocks are completed.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100