Filter Severity
Drops log records whose severity is lower than a configured minimum, keeping records at or above that threshold. An optional OTTL condition scopes which records the threshold is applied to; records that do not match the condition pass through untouched. Operates on logs only.
Supported Telemetry Types
Linux
✓
Windows
✓
macOS
✓
AIX
✓
Kubernetes Node
✓
Kubernetes Cluster
✓
Kubernetes Gateway
✓
OpenShift Node
✓
OpenShift Cluster
✓
OpenShift Gateway
✓
Google SecOps Pipelines
✓
Configuration

Logs
Severity
Enum: TRACE, DEBUG, INFO, WARN, ERROR, FATAL
Yes
TRACE
The minimum severity to keep. Log records with a lower severity are dropped. With the default TRACE, nothing is dropped on severity alone.
Condition
OTTL Condition
No
(empty)
An OTTL condition that must evaluate to true for the severity threshold to apply to a record. Leave empty to apply the threshold to all logs. Records that do not match are kept regardless of severity.
The severity order, from lowest to highest, is TRACE < DEBUG < INFO < WARN < ERROR < FATAL. Setting Severity to WARN, for example, drops TRACE, DEBUG, and INFO records while keeping WARN, ERROR, and FATAL.
Examples
Keep only WARN and above
Drop everything below WARN across all logs. Leave Condition empty so the threshold applies to every record.
Apply the threshold only to a subset of logs
Drop records below ERROR, but only for logs from the auth service. Records from any other service are kept regardless of severity because they do not match the condition.
Configuration Tips
The default Severity of
TRACEis a no-op for the threshold, since every level is at or aboveTRACE. Set a higher level for the processor to drop anything.Records with no severity set are treated as the lowest severity, so a non-
TRACEthreshold drops them. Set a Condition that excludes unset-severity records if you need to keep them.Use the Condition to limit the threshold to noisy sources rather than chaining multiple severity filters. One instance with a scoped condition is cheaper than several.
Troubleshooting
No logs are being dropped
Symptoms: log volume is unchanged after adding the processor.
Solutions:
Confirm Severity is set above
TRACE. The default keeps every record.If a Condition is set, verify it evaluates to true for the records you expect to filter. Records that do not match the condition are never dropped.
Too many logs are being dropped
Symptoms: records you wanted to keep are missing downstream.
Solutions:
Lower the Severity threshold, or scope it with a Condition so it applies only to the intended sources.
Check whether the dropped records have an unset severity. Unset severity is treated as the lowest level and is dropped by any non-
TRACEthreshold.
Severity mapping looks wrong
Symptoms: records are filtered at a different level than expected.
Solutions:
Verify the upstream parsing stage maps the source's severity into the OpenTelemetry severity number correctly. The threshold compares against the normalized OTel severity, not the raw text in the log body.
Standalone Processor
Related Resources
Last updated
Was this helpful?