github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update website/content/docs/troubleshoot/troubleshoot-services.mdx 

Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
pull/16385/head
Jeff Boruszak 2023-02-23 10:33:15 -06:00 committed by GitHub
parent 1405edeff9
commit 42e93d59f6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/troubleshoot/troubleshoot-services.mdx
View File

@ -97,6 +97,8 @@ In the example, troubleshooting upstream communication reveals that the `backend
The output from the troubleshooting process identifies service instances according to their [Consul DNS address](/consul/docs/discovery/dns#standard-lookup). Use the DNS information for failing services to diagnose the specific issues affecting the service instance.
For more information, refer to the [`consul troubleshoot` CLI documentation](/consul/commands/troubleshoot).
### Troubleshoot on Kubernetes
To troubleshoot service-to-service communication issues in deployments that use Kubernetes, retrieve the upstream information for the pod that is experiencing communication failures and use the upstream information to identify the proxy you want to perform the troubleshooting process on.