Rename jaeger to something not impl specific
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
## Suggestion
Not really a bug report or a feature request. Naming things is hard.
### What is the issue?
The linkerd `jaeger` extension provides integration for OpenTelemetry. It is now possible to configure `jaeger` without `jaeger` at all. Consider a rename to something more appropriate.
### Possible solution
I would suggest something like `tracing` or `apm` or `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 by locating the Linkerd jaeger extension and all references to its current name, then review how its OpenTelemetry integration is configured. Decide on an appropriate implementation-independent name and update the affected references consistently; done means the extension no longer depends on the jaeger name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- observability-sre
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100