Telemetry Pipeline plugins

Chronosphere Telemetry Pipeline provides extensions, called plugins, that let you customize and extend the capabilities of your telemetry data pipelines.

With these plugins, you can integrate with several data sources, collect and process different types of data, and output your data to various destinations. Whether you're dealing with logs, metrics, traces, or events, Telemetry Pipeline plugins can help you manage and monitor your data effectively. These plugins are flexible, letting you configure and customize them to suit your specific needs, and helping you scale from small-scale applications to large-scale distributed systems.

Plugins are available for both inputting telemetry data (source plugins) and sending processed telemetry data to external targets (destination plugins).

Add plugins to a pipeline

The source and destination plugins for each pipeline are listed in the inputs and outputs section of that pipeline's configuration file.

To add plugins to a pipeline, you can either edit a pipeline through the Telemetry Pipeline web interface, or edit the pipeline's configuration file directly. Each plugin includes a number of customizable settings, which are represented as key/value pairs within a configuration file. Many of these settings have default values.

For example, this snippet shows the default configuration settings for an OpenTelemetry source plugin:

pipeline:
  inputs:
    - Name: opentelemetry
      port: "8088"
      tag_from_uri: "false"
      buffer_chunk_size: 512K
      buffer_max_size: 4M
      successful_response_code: "201"
      tls.verify: on
      tls.debug: "1"
<...>

Descriptive names

To help keep track of your plugins, Telemetry Pipeline lets you add custom metadata to each plugin, including descriptive names. These descriptive names don't overwrite the default names assigned to each plugin. Instead, they're displayed under the plugin's default name in the Telemetry Pipeline web interface.