Free Report! Gartner® Hype Cycle™ for Monitoring and Observability.Read more

Filter Severity

Description

The Severity Filter processor can be used to filter out logs that do not meet a given severity threshold.

Supported Types

MetricsLogsTraces
✓

Configuration Table

ParameterTypeDefaultDescription
severityenumTRACEMinimum severity to match. Log entries with lower severities will be filtered.

Valid severity levels:

  • TRACE
  • INFO
  • WARN
  • ERROR
  • FATAL

Example Configuration

Filter out INFO and TRACE logs.

Web Interface

observIQ docs - Filter Severity - image 1

Standalone Processor

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Processor
3metadata:
4  id: severity-filter
5  name: severity-filter
6spec:
7  type: filter_severity
8  parameters:
9    - name: severity
10      value: WARN

Configuration with Embedded Processor

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Configuration
3metadata:
4  id: severity-filter
5  name: severity-filter
6  labels:
7    platform: linux
8spec:
9  sources:
10    - type: journald
11      parameters:
12        - name: units
13          value: []
14        - name: directory
15          value: ''
16        - name: priority
17          value: info
18        - name: start_at
19          value: end
20      processors:
21        - type: filter_severity
22          parameters:
23            - name: severity
24              value: WARN
25  selector:
26    matchLabels:
27      configuration: severity-filter