Collector for Linux default configuration
Configure the Splunk Distribution of OpenTelemetry Collector. There are a variety of default configuration files available, as well additional components that can be configured.
The Splunk Distribution of the OpenTelemetry Collector has the following components and services:
-
Receivers: Determine how you’ll get data into the Collector.
-
Processors: Configure which operations you’ll perform on data before it’s exported. For example, filtering.
-
Exporters: Set up where to send data to. It can be one or more backends or destinations.
-
Extensions: Extend the capabilities of the Collector.
Connectors: Connect two pipelines, consuming data as an exporter at the end of one pipeline and emitting data as a receiver at the start of another pipeline.
-
Services. It consists of two elements:
-
List of the extensions you’ve configured.
-
Pipelines: Path data will follow from reception, then through processing or modification, and finally exiting through exporters.
-
For more information, see Collector components.
The Collector configuration is stored in a YAML file and specifies the behavior of the different components and services. See an overview of the elements and pipelines in the default configuration in the following sections.
See Tutorial: Configure the Splunk Distribution of OpenTelemetry Collector on a Linux host to learn how to configure the Collector.
Default configuration
This is the default configuration file for the Linux (Debian/RPM) Installer collector packages:
https://raw.githubusercontent.com/signalfx/splunk-otel-collector/main/cmd/otelcol/config/collector/agent_config.yaml
Default pipelines
By default, ingested data follows these pipelines.
The following diagram shows the default logs pipeline:
Learn more about these receivers:
Learn more about these processors:
Learn more about these exporters:
Default pipelines for metrics
The following diagram shows the default metrics pipeline:
Learn more about these receivers:
Learn more about these processors:
Learn more about these exporters:
Default pipelines for traces
The following diagram shows the default traces pipeline:
Learn more about these receivers:
Learn more about these processors:
Learn more about these exporters:
Learn more
See also the following documents: