Custom

The Custom destination exports telemetry by inserting a raw OpenTelemetry exporter configuration directly into the collector pipeline. Use it to test a new exporter or to reach a backend that Bindplane does not yet support natively. You paste the exporter YAML and select which signals it handles. It supports logs, metrics, and traces.

Limitations

The Custom destination only works with exporters that are compiled into the Bindplane Collector. A configuration that references an exporter not present in the collector will fail to start. See the Included Components list for the components shipped in the collector, and the Exporter Syntax reference for the supported exporters and their configuration.

Because the YAML is inserted verbatim, Bindplane does not validate the exporter configuration. A malformed configuration or one that targets an unavailable exporter surfaces as a collector startup error rather than a Bindplane validation error.

Supported Telemetry Types

Metrics	Logs	Traces
✓	✓	✓

The signals this destination exports depend on the Choose Telemetry Type selection. Only the selected signals are routed to the pasted exporter.

Prerequisites

The Custom destination has no Bindplane-side prerequisites beyond the destination-specific requirements of whatever exporter you paste:

• The exporter must be one of the components compiled into the Bindplane Collector. See Included Components.
• Any credentials, endpoints, regions, or pre-created backend resources that the chosen exporter requires must be supplied inside the pasted configuration. Consult the upstream exporter's own documentation, linked from the Exporter Syntax reference.

Configuration

Exporter

Parameter	Type	Required	Default	Description
Choose Telemetry Type	Telemetry Selector	No	(empty)	Which signals the exporter receives. Any combination of Logs, Metrics, and Traces. Only the selected signals are routed to the exporter.
Configuration	YAML	Yes	—	The OpenTelemetry exporter configuration to insert. Enter any supported exporter and the YAML is inserted into the collector configuration verbatim. See Exporter Syntax.

Advanced

Parameter	Type	Required	Default	Description
Drop Raw Copy	Boolean	No	true	When enabled, the raw copy of the log stored in log.record.original is dropped before export. Applies to logs only.

Examples

Debug exporter for pipeline troubleshooting

The Debug exporter writes incoming telemetry to the collector's own log, which is useful for confirming that data reaches a destination. This example routes all three signals to it.

apiVersion: bindplane.observiq.com/v1
kind: Destination
metadata:
  name: debug
spec:
  type: custom
  parameters:
    - name: telemetry_types
      value:
        - Logs
        - Metrics
        - Traces
    - name: configuration
      value: 'debug:'

AWS Kinesis exporter

Bindplane does not offer a native Kinesis destination, but the Bindplane Collector includes the AWS Kinesis exporter. This example sends traces to a Kinesis stream.

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

Configuration Tips

• Confirm the exporter exists in the collector before applying. Cross-check the exporter key against the Included Components and Exporter Syntax references. An unavailable exporter fails at collector startup, not at apply time.
• Select only the signals the exporter actually supports. Routing an unsupported signal to an exporter produces collector errors.
• Leave Drop Raw Copy enabled to avoid double-storing log bodies. Disable it only when a downstream consumer needs the original log.record.original field.

Troubleshooting

Collector fails to start after applying the destination

Symptoms: the collector reports an unknown exporter type or a configuration parse error.

Solutions:

1. Verify the exporter is one of the Included Components in the Bindplane Collector.
2. Check the pasted YAML for indentation or syntax errors. The configuration is inserted verbatim and is not validated by Bindplane.

No telemetry reaches the backend

Symptoms: the exporter loads but the destination receives nothing.

Solutions:

1. Confirm Choose Telemetry Type includes the signals you are sending. Unselected signals are not routed to the exporter.
2. Verify the credentials, endpoint, and region inside the pasted configuration against the exporter's own documentation.

Backend rejects credentials or returns permission errors

Symptoms: the exporter logs authentication or authorization failures.

Solutions:

1. The Custom destination passes the configuration through unchanged. Resolve the credentials and permissions per the upstream exporter's documentation.

Standalone Destination

apiVersion: bindplane.observiq.com/v1
kind: Destination
metadata:
  name: custom
spec:
  type: custom
  parameters:
    - name: telemetry_types
      value:
        - Logs
        - Metrics
        - Traces
    - name: configuration
      value: 'debug:'
    - name: drop_raw_copy
      value: true

Related Resources

• Bindplane Collector exporters reference (Exporter Syntax)
• Bindplane Collector Included Components