Can Linkerd2 tap support printing response body?
Open
Nobody has claimed this yet.
area/tap
enhancement
pinned
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
What problem are you trying to solve?
I want to send the body content (decoded) lets say to elastic-search or write in to a file.
How should the problem be solved?
I execute the command: linkerd viz tap -n booksapp deploy/webapp -o wide ,and can see the response code and response length.Can it add body print options?
Any alternatives you've considered?
I haven't thought of it yet.
How would users interact with this feature?
No response
Would you like to work on this feature?
maybe
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 viz tap -n booksapp deploy/webapp -o wide command and trace how tap output is produced. Define the decoded response-body sources, output modes, and completion criteria before identifying the relevant implementation and tests.
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
- Needs clarification
- Newbie friendliness
- 25/100