From 00ec4e5ff3b1b18ab23ef0beedb4cbdfcada22b8 Mon Sep 17 00:00:00 2001 From: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> Date: Thu, 23 Feb 2023 10:32:11 -0600 Subject: [PATCH] Update website/content/docs/troubleshoot/troubleshoot-services.mdx Co-authored-by: Eric Haberkorn --- website/content/docs/troubleshoot/troubleshoot-services.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/troubleshoot/troubleshoot-services.mdx b/website/content/docs/troubleshoot/troubleshoot-services.mdx index db1c67930a..b6347189d5 100644 --- a/website/content/docs/troubleshoot/troubleshoot-services.mdx +++ b/website/content/docs/troubleshoot/troubleshoot-services.mdx @@ -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