Live Workshop: Integrate Google SecOps with Bindplane - Join Us on January 29th at 11 AM ET!Sign Up Now

Filter HTTP Status

Description

The HTTP Status processor can be used to filter out logs that contain a status code between a minimum and a maximum status code.

Supported Types

MetricsLogsTraces
✓

Configuration Table

ParameterTypeDefaultDescription
minimumenum100Minimum Status to match. Log entries with lower status codes will be filtered.
maximumenum599Maximum Status to match. Log entries with higher status codes will be filtered.

Valid Minimum Status Codes:

  • 100
  • 200
  • 300
  • 400
  • 500

Valid Maximum Status Codes:

  • 199
  • 299
  • 399
  • 499
  • 599

Example Configuration

Filter out all 1xx status codes and 2xx status codes.

Web Interface

observIQ docs - Filter HTTP Status - image 1

Standalone Processor

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Processor
3metadata:
4  id: http-status
5  name: http-status
6spec:
7  type: filter_http_status
8  parameters:
9    - name: maximum
10      value: 599
11    - name: minimum
12      value: 300

Configuration with Embedded Processor

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Configuration
3metadata:
4  id: http-status
5  name: http-status
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_http_status
22          parameters:
23            - name: maximum
24              value: 599
25            - name: minimum
26              value: 300
27  selector:
28    matchLabels:
29      configuration: http-status