github.com/observiq/bindplane-agent@v1.51.0/config/example.yaml (about)

     1  # 'receivers' specify configurations of receivers.
     2  # See the README for more information about the receivers available for configuration.
     3  receivers:
     4    # The hostmetrics receiver; this configuration will get cpu load metrics about the machine
     5    # the agent is running on every minute.
     6    # For more information on configuring the hostmetrics receiver, refer to the documentation here:
     7    # https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver
     8    hostmetrics:
     9      collection_interval: 1m
    10      scrapers:
    11        # Theses scrapers work on all operating systems
    12        load:
    13        filesystem:
    14        memory:
    15        network:
    16        # Remove these scrapers for macOS agents as they are not supported and will generate errors in the logs
    17        cpu:
    18        disk:
    19  
    20    # The syslog receiver; this configuration will listen on every network interface on port 514
    21    # for UDP syslog messages using the rfc3164 protocol.
    22    # For more information on configuring the syslog receiver, refer to the documentation here:
    23    # https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/syslogreceiver
    24    # syslog:
    25    #   protocol: "rfc3164"
    26    #   udp:
    27    #     listen_address: 0.0.0.0:514
    28  
    29  # 'processors' specify configurations of processors.
    30  # See the README for more information about the processors available for configuration.
    31  processors:
    32    # The batch processor; This processor will aggregate incoming metrics into a batch, releasing them if
    33    # a certain time has passed or if a certain number of entries have been aggregated.
    34    # For more information on configuring the batch processor, refer to the documentation here:
    35    # https://github.com/open-telemetry/opentelemetry-collector/tree/main/processor/batchprocessor
    36    batch:
    37  
    38  # 'exporters' specify configurations for certain exporters.
    39  # See the README for more information on the exporters available for configuration.
    40  exporters:
    41    # The logging exporter; This exporter logs to stdout.
    42    # For more information on configuring the logging exporter, refer to the documentation here:
    43    # https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/loggingexporter
    44    logging:
    45      verbosity: detailed
    46  
    47  # 'service' specifies how to construct the data pipelines using the configurations above.
    48  service:
    49    pipelines:
    50      # 'metrics' specifies a metrics pipeline; metrics are scraped using the 'hostmetrics' receiver,
    51      # which are aggregated into batches by the 'batch' processor,
    52      # and are exported using the 'logging' exporter, printing the metrics to stdout.
    53      metrics:
    54        receivers: [hostmetrics]
    55        processors: [batch]
    56        exporters: [logging]
    57  
    58      # `logs` specifies the logging pipeline; logs are received using the 'syslog' receiver,
    59      # which are then aggregated into batches by the 'batch' processor,
    60      # and are exported using the 'logging' exporter, printing the logs to stdout.
    61      # Both the batch configuration and logging configuration may be shared between the logs pipeline and
    62      # the metrics pipeline, as shown in this example.
    63      # logs:
    64      #   receivers: [syslog]
    65      #   processors: [batch]
    66      #   exporters: [logging]