How to use "Tap" in Linkerd2
@rmars is already working on this.
Since Feb 14, 2019.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
### What is the purpose of the post?
A tutorial to explain what the "Tap" command does in Linkerd2 and how to use it to improve observability / MTR reductions
### What should it talk about?
* What exactly does "Tap" do and show?
* What use cases does it address? Why did Linkerd build it?
* What are the options for using "Tap" (CLI, dashboard)?
* How does Tap interact / enhance service profiles and per-route metrics?
* How does Linkerd use "Tap" internally?
* What are some other amazing things you might be able to do with 'Tap'?
### Who is the target audience?
* [ ] Architect
* [x] SRE
* [x] Developers
### Are there any assets?
This should take the form of a tutorial and include specific applicable CLI commands and sequences to expose the dashboard. Using GIFs or codescreens to display the requisite actions is recommended.
### What are the dependencies?
TBD - depends on what the author thinks are appropriate here.
### Relevant Examples / References
https://github.com/linkerd/linkerd2/issues/1993
https://github.com/linkerd/linkerd2/issues/2106
https://github.com/linkerd/linkerd2/issues/1308
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.
Assessment
This issue has not been assessed yet.