Skip to content

docs(log-explorer): document that MatchedRules is not populated by cache rules#32041

Open
zeinjaber wants to merge 1 commit into
productionfrom
docs/DEE-3705-lex04-matchedrules-cache-rules
Open

docs(log-explorer): document that MatchedRules is not populated by cache rules#32041
zeinjaber wants to merge 1 commit into
productionfrom
docs/DEE-3705-lex04-matchedrules-cache-rules

Conversation

@zeinjaber

Copy link
Copy Markdown
Collaborator

What

Adds a FAQ entry to the Log Explorer FAQ page explaining that MatchedRules is only populated by security and transformation rules, not cache rules.

Why

Customers querying MatchedRules to investigate cache rule behavior get empty results with no explanation. The HTTP requests dataset field definition is auto-generated and cannot be edited directly, making the FAQ the appropriate location for this clarification.

Files changed

  • src/content/docs/log-explorer/faq.mdx — new FAQ entry before the query timeout section (+4 lines)

How to verify

Navigate to /log-explorer/faq/ and confirm the new entry appears near the top of the FAQ.

Closes DEE-3705

@zeinjaber zeinjaber requested a review from a team as a code owner July 13, 2026 15:05
@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Review

⚠️ 1 warning found in commit e5f59b2.

Fix in your agent
Fix the following review findings in PR #32041 (https://github.com/cloudflare/cloudflare-docs/pull/32041).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, fix all legitimate findings. For any you decide to skip,
post a comment on this PR with the finding ID and your reasoning.

---

## Style Guide Review

### Warnings (1)

#### SG-eaae7e15a872 · No trailing punctuation in headings
- **File:** `src/content/docs/log-explorer/faq.mdx` line 18
- **Issue:** Heading `## Why is the \`MatchedRules\` field empty for some requests?` ends with `?`
- **Fix:** Remove the `?` from the heading

Code Review

This code review is in beta and may not always be helpful — use your judgment.

No code review issues found.

Conventions

No convention issues found.

Style Guide Review

Warnings (1)
File Issue
log-explorer/faq.mdx line 18 No trailing punctuation in headings — Heading ## Why is the \MatchedRules` field empty for some requests?ends with?Fix: Remove the?` from the heading
Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command Description
/review Runs a review now. Incremental if a prior review exists, full if not.
/full-review Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.

@github-actions

Copy link
Copy Markdown
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/log-explorer/ @angelampcosta, @dcpena, @cloudflare/product-owners

@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant