Custom

Custom Processor

The Custom processor can be used to inject a custom processor configuration into a pipeline. A list of supported processors can be found here.

The Custom processor is useful for solving usecases not covered by BindPlane OP's other processor types.

Supported Types

MetricsLogsTraces
✓✓✓

The custom processor type can support all telemetry types, however, it is up to the user to enable / disable the correct types
based on the processor being used.

Configuration Table

ParameterTypeDefaultDescription
configurationyamlrequiredEnter any supported Processor and the YAML will be inserted into the configuration.
telemetry_typesenumsThe pipelines the processor should be used with.

Example Configuration

Inject the following resource processor configuration:

yaml
1resource:
2  attributes:
3    - action: upsert
4      key: custom
5      value: true

Web Interface

observIQ docs - Custom - image 1

Standalone Processor

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Processor
3metadata:
4  id: custom
5  name: custom
6spec:
7  type: custom
8  parameters:
9    - name: configuration
10      value: |
11        resource:
12          attributes:
13            - action: upsert
14              key: custom
15              value: true
16    - name: telemetry_types
17      value:
18        - Metrics
19        - Traces
20        - Logs

Configuration with Embedded Processor

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Configuration
3metadata:
4  id: custom
5  name: custom
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: custom
22          parameters:
23            - name: configuration
24              value: |
25                resource:
26                  attributes:
27                    - action: upsert
28                      key: custom
29                      value: true
30            - name: telemetry_types
31              value:
32                - Metrics
33                - Traces
34                - Logs
35  selector:
36    matchLabels:
37      configuration: custom