Skip to content

Commit cba13ee

Browse files
[Logpush] Small updates to the Logpush documentation (#26951)
* [Logpsuh] Update Logpush filters explanation in filters.mdx Clarify the behavior of Logpush filters in documentation. * [Logpush] Add warning about custom headers in Logpush Added a warning about the manual configuration of custom headers in Logpush. * Apply suggestions from code review * Update src/content/docs/logs/logpush/logpush-job/custom-fields.mdx --------- Co-authored-by: angelampcosta <[email protected]>
1 parent 36745d4 commit cba13ee

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

src/content/docs/logs/logpush/logpush-job/custom-fields.mdx

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,11 @@ Custom fields can be enabled via API or the Cloudflare dashboard.
2525
Custom fields are only available for the [HTTP requests dataset](/logs/logpush/logpush-job/datasets/zone/http_requests/).
2626
:::
2727

28+
:::note
29+
There is no way to automatically forward all custom headers in Logpush without manually specifying each one.
30+
Each request or response header must be individually configured using Custom Fields.
31+
:::
32+
2833
## Enable custom rules via API
2934

3035
Use the [Rulesets API](/ruleset-engine/rulesets-api/) to create a rule that configures custom fields. For more information on concepts like phases, rulesets, and rules, as well as the available API operations, refer to the [Ruleset Engine](/ruleset-engine/) documentation.

src/content/docs/logs/logpush/logpush-job/filters.mdx

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,13 @@ Here are some examples of how the logical operators can be implemented. `X`, `Y`
5353

5454
- (X AND Y) OR Z - `{"where":{"or":[{"and": [{X},{Y}]},{Z}]}}`
5555

56+
Logpush filters act as a pass-through gate, not an exclusion list. When multiple conditions are joined with AND:
57+
58+
- All conditions must evaluate to TRUE for the log to be pushed.
59+
- If any single condition is FALSE, the log is excluded.
60+
61+
A common misconception is interpreting the filter as `exclude logs matching ALL conditions` rather than `include logs matching ALL conditions`.
62+
5663
## Set filters via API or dashboard
5764

5865
Filters can be set via API or the Cloudflare dashboard. Note that using a filter is optional, but if used, it must contain the `where` key.

0 commit comments

Comments
 (0)