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 use cases not covered by the Honeycomb Telemetry Pipeline’s other processor types.
| Metrics | Logs | Traces |
|---|---|---|
| ✓ | ✓ | ✓ |
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.
| Parameter | Type | Default | Description |
|---|---|---|---|
| telemetry_types | telemetrySelector |
["Logs", "Metrics", "Traces"] |
The list of telemetry types the processor will act on. |
| configuration | yaml |
required | Enter any supported Processor and the YAML will be inserted into the configuration. |
Inject the following resource processor configuration:
resource:
attributes:
- action: upsert
key: custom
value: true
apiVersion: bindplane.observiq.com/v1
kind: Processor
metadata:
id: custom
name: custom
spec:
type: custom
parameters:
- name: configuration
value: |
resource:
attributes:
- action: upsert
key: custom
value: true
- name: telemetry_types
value:
- Metrics
- Traces
- Logs
apiVersion: bindplane.observiq.com/v1
kind: Configuration
metadata:
id: custom
name: custom
labels:
platform: linux
spec:
sources:
- type: journald
parameters:
- name: units
value: []
- name: directory
value: ''
- name: priority
value: info
- name: start_at
value: end
processors:
- type: custom
parameters:
- name: configuration
value: |
resource:
attributes:
- action: upsert
key: custom
value: true
- name: telemetry_types
value:
- Metrics
- Traces
- Logs
selector:
matchLabels:
configuration: custom