haskell-distributed / haskell-distributed/distributed-process
Support for distributed traces
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
It's very hard to know where a distributed-process application spends it's time. With something like OpenTracing or OpenTelemetry we have good tooling at our hands to analyse such traces.
We don't have to hard-code it down to OT or OTeL but supporting the concept of Traces, Spans and Links that would let a user plugin exporters might be a good way to integrate.
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 surveying the distributed-process codebase for existing instrumentation or extension points; the issue names no files, tests, or entry points. Clarify the intended Traces, Spans, and Links model and exporter plugin boundary, then define tests and documentation that demonstrate distributed trace support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- distributed-systems, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100