rfc: tap-style trace-logging
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
## Summary
Trace-level logging in the proxy is useful for debugging. Currently to achieve this, users redeploy the proxy with logging turned up:
https://github.com/linkerd/linkerd2/issues/2703#issuecomment-483758481
## Proposal
Introduce a CLI command that provides trace-level information from a specific proxy:
```bash
# linkerd trace [flags] (RESOURCE)
linkerd trace po/pod-foo-bar
linkerd trace -n emojivoto deploy/web
```
This command could follow a similar model to tap, and would complete the `linkerd metrics` command nicely.
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 reading the existing tap command and the linkerd metrics command, since the proposal says trace should follow tap's model. Done means defining and implementing a linkerd trace command that accepts a specific pod or deployment, including namespace support, and provides trace-level information from that proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100