akash-network / akash-network/console
Setup OTEL for notification service
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 264
- Forks
- 94
- Avg merge
- 18h 49m
- Merged PRs (30d)
- 297
Description
We're currently missing some convenience observability features in notification service, specifically tracing data. This complicates debugging and monitoring regularly.
Acceptance criteria:
- auto instrumentations are set up
trace_idis sent over with eventstrace_idis picked up by handlers and handlers run in their context
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 locating the notification service's event publishing and handler entry points, then review how tracing and context are currently configured. The work is done when auto-instrumentation is enabled, events carry a trace_id, and handlers process events within the corresponding trace context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100