· 6 years ago · Oct 02, 2019, 12:22 AM
1###################### Metricbeat Configuration Example #######################
2
3# This file is an example configuration file highlighting only the most common
4# options. The metricbeat.reference.yml file from the same directory contains all the
5# supported options with more comments. You can use it as a reference.
6#
7# You can find the full configuration reference here:
8# https://www.elastic.co/guide/en/beats/metricbeat/index.html
9
10#========================== Modules configuration ============================
11
12metricbeat.config.modules:
13 # Glob pattern for configuration loading
14 path: ${path.config}/modules.d/*.yml
15
16 # Set to true to enable config reloading
17 reload.enabled: false
18
19 # Period on which files under path should be checked for changes
20 #reload.period: 10s
21
22#==================== Elasticsearch template setting ==========================
23
24setup.template.settings:
25 index.number_of_shards: 1
26 index.codec: best_compression
27 #_source.enabled: false
28
29#================================ General =====================================
30
31# The name of the shipper that publishes the network data. It can be used to group
32# all the transactions sent by a single shipper in the web interface.
33#name:
34
35# The tags of the shipper are included in their own field with each
36# transaction published.
37#tags: ["service-X", "web-tier"]
38
39# Optional fields that you can specify to add additional information to the
40# output.
41#fields:
42# env: staging
43
44
45#============================== Dashboards =====================================
46# These settings control loading the sample dashboards to the Kibana index. Loading
47# the dashboards is disabled by default and can be enabled either by setting the
48# options here, or by using the `-setup` CLI flag or the `setup` command.
49#setup.dashboards.enabled: false
50
51# The URL from where to download the dashboards archive. By default this URL
52# has a value which is computed based on the Beat name and version. For released
53# versions, this URL points to the dashboard archive on the artifacts.elastic.co
54# website.
55#setup.dashboards.url:
56
57#============================== Kibana =====================================
58
59# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
60# This requires a Kibana endpoint configuration.
61setup.kibana:
62
63 # Kibana Host
64 # Scheme and port can be left out and will be set to the default (http and 5601)
65 # In case you specify and additional path, the scheme is required: http://localhost:5601/path
66 # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
67 host: "192.168.0.171:5601"
68
69 # Kibana Space ID
70 # ID of the Kibana Space into which the dashboards should be loaded. By default,
71 # the Default Space will be used.
72 #space.id:
73
74#============================= Elastic Cloud ==================================
75
76# These settings simplify using metricbeat with the Elastic Cloud (https://cloud.elastic.co/).
77
78# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
79# `setup.kibana.host` options.
80# You can find the `cloud.id` in the Elastic Cloud web UI.
81#cloud.id:
82
83# The cloud.auth setting overwrites the `output.elasticsearch.username` and
84# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
85#cloud.auth:
86
87#================================ Outputs =====================================
88
89# Configure what output to use when sending the data collected by the beat.
90
91#-------------------------- Elasticsearch output ------------------------------
92output.elasticsearch:
93 # Array of hosts to connect to.
94 hosts: ["192.168.0.171:9200"]
95
96 # Enabled ilm (beta) to use index lifecycle management instead daily indices.
97 #ilm.enabled: false
98
99 # Optional protocol and basic auth credentials.
100 #protocol: "https"
101 #username: "elastic"
102 #password: "changeme"
103
104#----------------------------- Logstash output --------------------------------
105#output.logstash:
106 # The Logstash hosts
107 #hosts: ["localhost:5044"]
108
109 # Optional SSL. By default is off.
110 # List of root certificates for HTTPS server verifications
111 #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
112
113 # Certificate for SSL client authentication
114 #ssl.certificate: "/etc/pki/client/cert.pem"
115
116 # Client Certificate Key
117 #ssl.key: "/etc/pki/client/cert.key"
118
119#================================ Processors =====================================
120
121# Configure processors to enhance or manipulate events generated by the beat.
122
123processors:
124 - add_host_metadata: ~
125 - add_cloud_metadata: ~
126
127#================================ Logging =====================================
128
129# Sets log level. The default log level is info.
130# Available log levels are: error, warning, info, debug
131#logging.level: debug
132
133# At debug level, you can selectively enable logging only for some components.
134# To enable all selectors use ["*"]. Examples of other selectors are "beat",
135# "publish", "service".
136#logging.selectors: ["*"]
137
138#============================== Xpack Monitoring ===============================
139# metricbeat can export internal metrics to a central Elasticsearch monitoring
140# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
141# reporting is disabled by default.
142
143# Set to true to enable the monitoring reporter.
144#xpack.monitoring.enabled: false
145
146# Uncomment to send the metrics to Elasticsearch. Most settings from the
147# Elasticsearch output are accepted here as well. Any setting that is not set is
148# automatically inherited from the Elasticsearch output configuration, so if you
149# have the Elasticsearch output configured, you can simply uncomment the
150# following line.
151#xpack.monitoring.elasticsearch: