Troubleshooting the Envoy proxy
As you can see, the Envoy proxy plays an integral role in AWS App Mesh. So being able to troubleshoot it is a critical skill. By default, Envoy logging is set to informational and while we are debugging, the first thing to do is to increase this logging level.
If you have control over the Pod, then you can adjust the ENVOY_LOG_LEVEL
variable as we did when we deployed the VirtualGateway
for the myapp services, as shown in the following manifest snippet:
env: - name: ENVOY_LOG_LEVEL value: "debug"
Those Pods that are injected into a namespace come with the Envoy admin port 9901
enabled so we can use the kubectl port-forward
command to map a local port to the admin port. The following command is an example of connecting to a Pod in the green
namespace...