Skip to main content
The filter transform drops or keeps events based on conditions you define. Use it to remove health checks, exclude debug logs, or keep only production traffic before data reaches your sinks.

Quick start

Drop events where path equals /health:

Actions

Operators

Multiple conditions

When you need more than one condition, use the conditions array and set match to control how they combine:

Examples

Keep only errors from production:
Drop events matching a regex:
Keep events where a user ID exists:
Filter on nested fields (dot notation):

Reference

Non-JSON messages pass through unchanged — conditions only evaluate against JSON fields.