interledger / interledger/rafiki
Investigate Telemetry Tracing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 358
- Forks
- 116
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 4
Description
tracing reported broken in https://github.com/interledger/rafiki/pull/3960
Separately, and not caused by anything in this PR: telemetry tracing looks broken on main any time ENABLE_TELEMETRY_TRACES=true. The backend has sdk-node 0.217.0 pulling v2-era otlp-transformer alongside the v1-era exporter-trace-otlp-grpc / exporter-metrics-otlp-grpc, and trace export throws on clashing protobufjs globals. Bumping the two grpc exporters to ^0.221.0 fixes that crash but trades it for another, since v1's Span has no instrumentationScope field and the v2-era serializer requires it. Nothing catches this today because service.test.ts mocks the otel packages wholesale and CI never enables telemetry. Worth a look by whoever owns telemetry.
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 the backend telemetry dependencies and service.test.ts, then reproduce tracing with ENABLE_TELEMETRY_TRACES=true instead of the current wholesale OpenTelemetry mocks. Trace export should work without protobuf or instrumentationScope errors, and tests should cover the enabled telemetry path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100