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