https://docs.airlock.com/microgateway/5.2/troubleshooting/ This troubleshooting chapter provides problem determination and resolution information for issues that are commonly encountered. The articles in this chapter can help you to determine why something does not work as expected and explain how to resolve the problem. Troubleshooting works best when you choose a systematic approach to solving a problem. Info If you encounter a problem that you cannot solve by yourself, even after you determine its cause, you can contact our service department. Hugo en-US https://docs.airlock.com/microgateway/5.2/troubleshooting/analyze-configuration-issues/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.airlock.com/microgateway/5.2/troubleshooting/analyze-configuration-issues/ General approach Troubleshooting Microgateway resources follows the same problem-solving approach as troubleshooting other Kubernetes workloads: Check resource conditions for potential problems. Start with inspecting the Gateway resource. Note: If the Gateway resource is not accessible due to missing permissions, skip this step. Continue with inspecting HTTPRoute resources. Finish with inspecting policy resources. Review events that may point to pending or unresolved issues. https://docs.airlock.com/microgateway/5.2/troubleshooting/record-http-traffic/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.airlock.com/microgateway/5.2/troubleshooting/record-http-traffic/ The Envoy Tap filter allows to interpose on and record HTTP traffic that the Microgateway receives. For further details, see official Envoy Tap filter documentation. Setup the Tap filter Tap filter configuration Create a CR EnvoyHTTPFilter with a Tap filter configuration. 1 2 3 4 5 6 7 8 9 10 11 12 apiVersion: microgateway.airlock.com/v1alpha1 kind: EnvoyHTTPFilter metadata: name: tap-filter spec: value: name: envoy.filters.http.tap typed_config: "@type": type.googleapis.com/envoy.extensions.filters.http.tap.v3.Tap common_config: admin_config: config_id: tap_filter_config Create a CR EnvoyExtensionPolicy and refer to the desired HTTPRoute. Reference the CR EnvoyHTTPFilter. https://docs.airlock.com/microgateway/5.2/troubleshooting/envoy-administration-interface/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.airlock.com/microgateway/5.2/troubleshooting/envoy-administration-interface/ The Microgateway Engine is built on the basis of the Envoy proxy and enriched with Airlock-specific features. When analyzing complex problems, it can be helpful to have more insight and check the current configuration, print the memory usage and list the server information or other information. The above and other information is accessible through the Envoy Administration interface. Setup port forward To access the Envoy Administration interface, a port forward must be setup.