Add troubleshooting docs that point to the endpoints command
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
As part of the 2.3 release, there will be a new `endpoints` command that allows debugging of the current state of service discovery. This should be added to the troubleshooting docs and flesh out the post-install story of "why can't my service talk to another".
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
Locate the troubleshooting documentation and review the new `endpoints` command described in the issue. Add guidance for post-install debugging when one service cannot communicate with another, pointing readers to that command; the troubleshooting flow should explain why and when to use it.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100