From e5f59b2be2621a214824895a9ba6baf1fa15f050 Mon Sep 17 00:00:00 2001 From: zeinjaber Date: Mon, 13 Jul 2026 18:04:49 +0300 Subject: [PATCH] docs(log-explorer): document that MatchedRules is not populated by cache rules Closes DEE-3705 --- src/content/docs/log-explorer/faq.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/docs/log-explorer/faq.mdx b/src/content/docs/log-explorer/faq.mdx index a19c65eb5fd..2280aa45064 100644 --- a/src/content/docs/log-explorer/faq.mdx +++ b/src/content/docs/log-explorer/faq.mdx @@ -15,6 +15,10 @@ import { DashButton } from "~/components"; All fields listed in [Datasets](/logs/logpush/logpush-job/datasets/) for the [supported datasets](/log-explorer/manage-datasets/#supported-datasets) are viewable in Log Explorer. +## Why is the `MatchedRules` field empty for some requests? + +`MatchedRules` is populated only by security and transformation rules (WAF, Rate Limiting, Transform Rules, Snippets). Cache rules do not populate this field. If you are investigating cache behavior, use the `Cache*` fields such as `CacheCacheStatus` instead. + ## Why does my query not complete or time out? Log Explorer performs best when query parameters focus on narrower ranges of time. You may experience query timeouts when your query would return a large quantity of data. Consider refining your query to improve performance.