-
Turn logging on, if it isn’t, with
scopematchedand an environment in the WAF’s project:"logging": { "scope": "matched", "environment": "production" } -
Search the environment for the WAF’s blocks:
ezgh obs search --environment production --service ezgh.waf --from 1h --contains '"action":"block"'In the console, Find blocked requests on a WAF’s Logging tab opens its logs in Observability.
-
Read a record’s
terminatingRuleandmatchedRules: they name the rule that blocked the request, with its set. Itspath,query,clientIpanduserAgentshow what was sent and by whom.
To narrow it down, add --matches with a regular expression, such as "path":"/checkout, or another
filter of ezgh obs search.
A legitimate request was blocked
- By a managed rule: add a rule override
for its ID,
off(orlog, outsideezgh/core). - By a custom rule: change its conditions, or add an
allowrule above it for the request. - To check a change first: set the set’s or the WAF’s
modetolog. Records then showactionlogfor what it would have blocked.