Custom

Description

This Custom destination can be used to directly configure an OpenTelemetry Exporter. The Custom destination is useful for testing new Exporters or for fulfilling a niche use case that is not supported by BindPlane natively.

note

The Custom Destination can only be used with components that are present in the BindPlane Agent. See the Included Components documentation for a list of supported components.

Supported Types

MetricsLogsTracesBindplane Agent
v1.30.0+

Configuration

FieldDescription
Telemetry TypesThe kind of telemetry that will be sent to the Exporter. Can be any combination of metrics, logs, and traces.
ConfigurationThe YAML configuration for the Exporter.

Example Configuration

Logging Exporter

The Logging Exporter is useful for debugging a pipeline, allowing the user to see realtime telemetry when viewing the agent's log file. It can be configured using the Custom Destination.

Web Interface

observIQ docs - Custom Destination Logging - image 1

Standalone Destination

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Destination
3metadata:
4  name: logging
5spec:
6  type: custom:1
7  parameters:
8    - name: telemetry_types
9      value:
10        - Logs
11        - Metrics
12        - Traces
13    - name: configuration
14      value: 'logging:'

AWS Kinesis Exporter

At the time of this writing, BindPlane does not support the Kinesis Exporter natively. However, the bindplane-agent does support the Kinesis Exporter.

Web Interface

observIQ docs - Kinesis Destination Logging - image 1

Standalone Destination

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Destination
3metadata:
4  name: kinesis
5spec:
6  type: custom:1
7  parameters:
8    - name: telemetry_types
9      value:
10        - Logs
11        - Metrics
12        - Traces
13    - name: configuration
14      value: |-
15        awskinesis:
16          aws:
17            stream_name: raw-trace-stream
18            region: us-east-1
19            role: arn:test-role