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 Collector. See the Included Components documentation for a list of supported components.

Supported Types

Logs	Metrics	Traces	Bindplane Collector
✓	✓	✓	v1.30.0+

Configuration

Field	Description
Choose Telemetry Type	The kind of telemetry that will be sent to the Exporter. Can be any combination of logs, metrics, and traces.
Configuration	The 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 collector's log file. It can be configured using the Custom Destination.

Web Interface

Standalone Destination

apiVersion: bindplane.observiq.com/v1
kind: Destination
metadata:
  name: logging
spec:
  type: custom:1
  parameters:
    - name: telemetry_types
      value:
        - Logs
        - Metrics
        - Traces
    - name: configuration
      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

Standalone Destination

apiVersion: bindplane.observiq.com/v1
kind: Destination
metadata:
  name: kinesis
spec:
  type: custom:1
  parameters:
    - name: telemetry_types
      value:
        - Logs
        - Metrics
        - Traces
    - name: configuration
      value: |-
        awskinesis:
          aws:
            stream_name: raw-trace-stream
            region: us-east-1
            role: arn:test-role