optional to enable tracing for linkerd/namerd/namer/tracing requests
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 5.3k
- Forks
- 494
- PR merge metrics
- No merged PRs in 30d
Description
linkerd currently disables tracing for its own internal requests involving linkerd, namerd, namers, and tracing. the intent is to keep a user's zipkin or tracing data strictly for their own service requests.
however, there are cases where tracing for these internal requests is useful. specifically, for debugging linkerd/namerd issues. propose adding a config option to enable tracing for internal requests. this change would probably start with a search for all calls to `Trace.letClear`.
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
Search the codebase for all calls to `Trace.letClear` and trace how internal linkerd, namerd, namer, and tracing requests are identified. Find the configuration entry point that can control this behavior. Done means a configuration option enables or disables tracing for those internal requests while preserving the current default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100