Skip to content

Latest commit

 

History

History
194 lines (143 loc) · 6.62 KB

collector-config-ootb.rst

File metadata and controls

194 lines (143 loc) · 6.62 KB

By default, ingested data follows these pipelines.

Default pipelines for logs

The following diagram shows the default logs pipeline:

.. mermaid::

   flowchart LR

      accTitle: Default logs pipeline diagram
      accDescr: Receivers send logs to the logs/memory_limiter processor. The logs/memory_limiter processor sends logs to the batch processor, and the batch processor sends logs to the resource detection processor. The resource detection processor sends logs to the exporter. The SignalFx logs pipeline follows the same steps, but uses internal receivers, processors, and exporters to send logs.

      %% LR indicates the direction (left-to-right)

      %% You can define classes to style nodes and other elements
      classDef receiver fill:#00FF00
      classDef processor fill:#FF9900
      classDef exporter fill:#FF33FF

      %% Each subgraph determines what's in each category
      subgraph Receivers
         direction LR
         logs/signalfx/signalfx/in:::receiver
         logs/signalfx/smartagent/processlist:::receiver
         logs/fluentforward:::receiver
         logs/otlp:::receiver
      end

      subgraph Processor
         direction LR
         logs/signalfx/memory_limiter:::processor --> logs/signalfx/batch:::processor --> logs/signalfx/resourcedetection:::processor
         logs/memory_limiter:::processor --> logs/batch:::processor --> logs/resourcedetection:::processor
      end

      subgraph Exporters
         direction LR
         logs/signalfx/signalfx/out:::exporter
         logs/splunk_hec:::exporter
      end

      %% Connections beyond categories are added later
      logs/signalfx/signalfx/in --> logs/signalfx/memory_limiter
      logs/signalfx/resourcedetection --> logs/signalfx/signalfx/out
      logs/signalfx/smartagent/processlist --> logs/signalfx/memory_limiter
      logs/fluentforward --> logs/memory_limiter
      logs/resourcedetection --> logs/splunk_hec
      logs/otlp --> logs/memory_limiter

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:

.. mermaid::

   flowchart LR

      accTitle: Default metric pipeline diagram
      accDescr: Receivers send logs to the metrics/memory_limiter processor. The metrics/memory_limiter processor sends metrics to the batch processor, and the batch processor sends metrics to the resource detection processor. The resource detection processor sends metrics to the exporter. The internal metrics pipeline follows the same steps, but uses internal receivers, processors, and exporters to send metrics.

      %% LR indicates the direction (left-to-right)

      %% You can define classes to style nodes and other elements
      classDef receiver fill:#00FF00
      classDef processor fill:#FF9900
      classDef exporter fill:#FF33FF

      %% Each subgraph determines what's in each category
      subgraph Receivers
         direction LR
         metrics/hostmetrics:::receiver
         metrics/otlp:::receiver
         metrics/signalfx/in:::receiver
         metrics/internal/prometheus/internal:::receiver
      end

      subgraph Processor
         direction LR
         metrics/memory_limiter:::processor --> metrics/batch:::processor --> metrics/resourcedetection:::processor
         metrics/internal/memory_limiter:::processor --> metrics/internal/batch:::processor --> metrics/internal/resourcedetection:::processor
      end

      subgraph Exporters
         direction LR
         metrics/signalfx/out:::exporter
         metrics/internal/signalfx/out:::exporter
      end

      %% Connections beyond categories are added later
      metrics/hostmetrics --> metrics/memory_limiter
      metrics/resourcedetection --> metrics/signalfx/out
      metrics/otlp --> metrics/memory_limiter
      metrics/signalfx/in --> metrics/memory_limiter
      metrics/internal/prometheus/internal --> metrics/internal/memory_limiter
      metrics/internal/resourcedetection --> metrics/internal/signalfx/out

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:

.. mermaid::

   flowchart LR

      accTitle: Default traces pipeline diagram
      accDescr: Receivers send traces to the traces/memory_limiter processor. The traces/memory_limiter processor sends traces to the batch processor, and the batch processor sends traces to the resource detection processor. The resource detection processor sends traces to the Splunk APM exporter and the SignalFx exporter.

      %% LR indicates the direction (left-to-right)

      %% You can define classes to style nodes and other elements
      classDef receiver fill:#00FF00
      classDef processor fill:#FF9900
      classDef exporter fill:#FF33FF

      %% Each subgraph determines what's in each category
      subgraph Receivers
         direction LR
         traces/jaeger:::receiver
         traces/otlp:::receiver
         traces/zipkin:::receiver
      end

      subgraph Processor
         direction LR
         traces/memory_limiter:::processor --> traces/batch:::processor --> traces/resourcedetection:::processor
      end

      subgraph Exporters
         direction LR
         traces/otlphttp:::exporter
         traces/signalfx/out:::exporter
      end

      %% Connections beyond categories are added later
      traces/jaeger --> traces/memory_limiter
      traces/otlp --> traces/memory_limiter
      traces/zipkin --> traces/memory_limiter
      traces/resourcedetection --> traces/otlphttp
      traces/resourcedetection --> traces/signalfx/out

Learn more about these receivers:

Learn more about these processors:

Learn more about these exporters: