digidem / digidem/comapeo-core-react-native
Sentry: verify @comapeo/core OTel span forwarding (Phase 4)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 8h 24m
- Merged PRs (30d)
- 9
Description
Part of #74. Blocked on comapeo-core#1051 landing. Verification only — most useful once #75's debug toggle exists, because core's spans need a per-RPC parent span to attach to (§11.3).
Spec: docs/sentry-integration-plan.md Phase 4.
@comapeo/core is gaining OpenTelemetry instrumentation — spans describing its internal operations (sync, indexing, hypercore). Once that lands, Sentry should pick those spans up automatically and nest them under our RPC traces, giving deep visibility inside core operations.
Deliverables
- Bump
@comapeo/coreinbackend/package.jsononce PR #1051 ships - With
debugon, verify core's spans appear in Sentry nested under the RPC transaction - Document any tracing-config overrides needed
- Confirm the full chain: JS client span → backend RPC transaction → core operation spans
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
Read docs/sentry-integration-plan.md Phase 4 and inspect backend/package.json. Wait for comapeo-core#1051 and the #75 debug toggle, then enable debug and verify the full JS client → RPC transaction → core span chain in Sentry. Document any tracing-config overrides and confirm the dependency bump.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, kotlin
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100