Complimentary Gartner® Report! 'A CTO's Guide to Open-Source Software: Answering the Top 10 FAQs.'Read more

Custom

Custom Extension

The Custom extension can be used to inject a custom OTel extension into a Configuration. A List of supported extensions can be found here.

Configuration Table

ParameterTypeDefaultDescription
telemetry_typestelemetrySelector[]Choose Telemetry Type.
configurationyamlrequiredEnter any supported Extension and the YAML will be inserted into the configuration.

Example Configuration

In this example, we use the Custom extension type to inject the following health check extension.

yaml
1healthcheck:
2  endpoint: 0.0.0.0:13133
3  path: /health

Web Interface

observIQ docs - Custom Extension - image 1

Standalone Extension

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Extension
3metadata:
4  name: custom-health-check
5  spec:
6    type: custom
7    parameters:
8      - name: telemetry_types
9        value: ['Logs', 'Metrics', 'Traces']
10      - name: configuration
11        value: |
12          health_check:
13            endpoint: 0.0.0.0:13133
14            path: /health

Configuration with Embedded Extension

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Configuration
3metadata:
4  name: custom-configuration-with-extensions
5  labels:
6    platform: linux
7spec:
8  extensions:
9    - type: custom
10      parameters:
11        - name: telemetry_types
12          value: ['Logs', 'Metrics', 'Traces']
13        - name: configuration
14          value: |
15            health_check:
16              endpoint: 0.0.0.0:13133
17              path: health