EnvoyFilter present in config but not affecting traffic

EnvoyFilter appears in config dump but does not affect traffic behavior, typically because it is on the wrong filter chain (Envoy has multiple chains per listener for different ports/SNI), incorrect filter order (e.g., auth filter must come before router), or mismatched type URLs (v2 vs v3)

Verify the filter is on the correct filter chain for the target traffic. For filters requiring specific ordering (like auth), use INSERT_BEFORE with envoy.filters.http.router as reference. Ensure @type URL matches proto type (v3 configuration requires v3 type URLs). Review access logs to determine which filter chain handles target requests.