Bring-your-own-tracing with the jaeger extension
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
By default, the linkerd-jaeger extension installs an OpenCensus collector and a Jaeger backend.
However, for users who have an existing Jaeger backend, it should be possible to configure the linkerd-jaeger extension to have the oc-collector send traces to that existing Jaeger backend.
Similarly, for users who have an existing OpenCensus collector, it should be possible to configure the jaeger-injector to point injected proxies at that existing collector.
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 linkerd-jaeger extension configuration, the oc-collector, and the jaeger-injector paths described in the issue. Trace how each currently selects its backend or collector, then verify that existing Jaeger and OpenCensus endpoints can be configured independently while the current defaults continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100