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: Eric Haberkorn <erichaberkorn@gmail.com>
pull/16385/head
Jeff Boruszak 2023-02-23 10:32:11 -06:00 committed by GitHub
parent 51b6f5009f
commit 00ec4e5ff3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 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

@ -44,7 +44,7 @@ When troubleshooting service-to-service communication issues, be aware of the fo
- The troubleshooting tool does not check service intentions. For more information about intentions, including precedence and match order, refer to [service mesh intentions](/consul/docs/connect/intentions).
- The troubleshooting tool validates one direct connection between a downstream service and an upstream service. You must run the `consul troubleshoot` command with the Envoy ID for an individual upstream service. It does support validating multiple connections simultaneously.
- Because it validates direct communication between two Envoy proxies, the troubleshooting tool does not support checks for service-to-service connections when communication between the services passes through a mesh gateway or a terminating gateway.
- The troubleshooting tool only validates Envoy configurations for sidecar proxies. This means the troubleshooting tool does not validate Envoy configurations on upstream proxies such as mesh gateways and terminating gateways.
## Usage