How to debug an EnvoyFilter?-CodePudding

I have this filter:

apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: proper
  namespace: istio-system
spec:
  workloadSelector:
    labels:
      app: istio-ingressgateway
  configPatches:
    - applyTo: NETWORK_FILTER
      match:
        context: GATEWAY
        listener:
          filterChain:
            filter:
              name: "envoy.http_connection_manager"
      patch:
        operation: INSERT_BEFORE
        value: # lua filter specification
          name: envoy.lua
          typed_config:
            "@type": "type.googleapis.com/envoy.config.filter.http.lua.v2.Lua"
            inlineCode: |
              function envoy_on_request(request_handle)
                 request_handle:logDebug("Hello World")
              end

I am checking the logs for the gateway and it does not look like the filter is used. How do I debug an EnvoyFilter? Where can I see what filters are applied each request?

CodePudding user response：

This topic is very well described in the documentation:

The simplest kind of Istio logging is Envoy’s access logging. Envoy proxies print access information to their standard output. The standard output of Envoy’s containers can then be printed by the kubectl logs command.

You have asked:

Where can I see what filters are applied each request?

Based on this issue on github:

There is no generic mechanism.

It follows that if you wanted to see what filter was applied to each request, you would have to create your custom solution.

However, without any problem, you can get logs about each request based on this fragment in the documentation:

If you used an IstioOperator CR to install Istio, add the following field to your configuration:

spec:
  meshConfig:
    accessLogFile: /dev/stdout

Otherwise, add the equivalent setting to your original istioctl install command, for example:

istioctl  install  <flags-you-used-to-install-Istio> --set meshConfig.accessLogFile=/dev/stdout

You can also choose between JSON and text by setting accessLogEncoding to JSON or TEXT. You may also want to customize the format of the access log by editing accessLogFormat.

Refer to global mesh options for more information on all three of these settings:

meshConfig.accessLogFile
meshConfig.accessLogEncoding
meshConfig.accessLogFormat

You can also change access log format and test the access log from linked instructions.