· 6 years ago · Dec 09, 2019, 07:14 AM
1###################### Filebeat Configuration Example #########################
2
3# This file is an example configuration file highlighting only the most common
4# options. The filebeat.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/filebeat/index.html
9
10# For more available modules and options, please see the filebeat.reference.yml sample
11# configuration file.
12
13#=========================== Filebeat inputs =============================
14
15filebeat.inputs:
16
17# Each - is an input. Most options can be set at the input level, so
18# you can use different inputs for various configurations.
19# Below are the input specific configurations.
20
21- type: log
22
23 # Change to true to enable this input configuration.
24 enabled: false
25
26 # Paths that should be crawled and fetched. Glob based paths.
27 paths:
28 - /var/log/*.log
29 #- c:\programdata\elasticsearch\logs\*
30
31 # Exclude lines. A list of regular expressions to match. It drops the lines that are
32 # matching any regular expression from the list.
33 #exclude_lines: ['^DBG']
34
35 # Include lines. A list of regular expressions to match. It exports the lines that are
36 # matching any regular expression from the list.
37 #include_lines: ['^ERR', '^WARN']
38
39 # Exclude files. A list of regular expressions to match. Filebeat drops the files that
40 # are matching any regular expression from the list. By default, no files are dropped.
41 #exclude_files: ['.gz$']
42
43 # Optional additional fields. These fields can be freely picked
44 # to add additional information to the crawled log files for filtering
45 #fields:
46 # level: debug
47 # review: 1
48
49 ### Multiline options
50
51 # Multiline can be used for log messages spanning multiple lines. This is common
52 # for Java Stack Traces or C-Line Continuation
53
54 # The regexp Pattern that has to be matched. The example pattern matches all lines starting with [
55 #multiline.pattern: ^\[
56
57 # Defines if the pattern set under pattern should be negated or not. Default is false.
58 #multiline.negate: false
59
60 # Match can be set to "after" or "before". It is used to define if lines should be append to a pattern
61 # that was (not) matched before or after or as long as a pattern is not matched based on negate.
62 # Note: After is the equivalent to previous and before is the equivalent to to next in Logstash
63 #multiline.match: after
64
65
66#============================= Filebeat modules ===============================
67
68filebeat.config.modules:
69 # Glob pattern for configuration loading
70 path: ${path.config}/modules.d/*.yml
71
72 # Set to true to enable config reloading
73 reload.enabled: false
74
75 # Period on which files under path should be checked for changes
76 #reload.period: 10s
77
78#==================== Elasticsearch template setting ==========================
79
80setup.template.settings:
81 index.number_of_shards: 1
82 #index.codec: best_compression
83 #_source.enabled: false
84
85#================================ General =====================================
86
87# The name of the shipper that publishes the network data. It can be used to group
88# all the transactions sent by a single shipper in the web interface.
89#name:
90
91# The tags of the shipper are included in their own field with each
92# transaction published.
93#tags: ["service-X", "web-tier"]
94
95# Optional fields that you can specify to add additional information to the
96# output.
97#fields:
98# env: staging
99
100
101#============================== Dashboards =====================================
102# These settings control loading the sample dashboards to the Kibana index. Loading
103# the dashboards is disabled by default and can be enabled either by setting the
104# options here or by using the `setup` command.
105#setup.dashboards.enabled: false
106
107# The URL from where to download the dashboards archive. By default this URL
108# has a value which is computed based on the Beat name and version. For released
109# versions, this URL points to the dashboard archive on the artifacts.elastic.co
110# website.
111#setup.dashboards.url:
112
113#============================== Kibana =====================================
114
115# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
116# This requires a Kibana endpoint configuration.
117setup.kibana:
118
119 # Kibana Host
120 # Scheme and port can be left out and will be set to the default (http and 5601)
121 # In case you specify and additional path, the scheme is required: http://localhost:5601/path
122 # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
123 #host: "localhost:5601"
124
125 # Kibana Space ID
126 # ID of the Kibana Space into which the dashboards should be loaded. By default,
127 # the Default Space will be used.
128 #space.id:
129
130#============================= Elastic Cloud ==================================
131
132# These settings simplify using Filebeat with the Elastic Cloud (https://cloud.elastic.co/).
133
134# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
135# `setup.kibana.host` options.
136# You can find the `cloud.id` in the Elastic Cloud web UI.
137#cloud.id:
138
139# The cloud.auth setting overwrites the `output.elasticsearch.username` and
140# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
141#cloud.auth:
142
143#================================ Outputs =====================================
144
145# Configure what output to use when sending the data collected by the beat.
146
147#-------------------------- Elasticsearch output ------------------------------
148output.elasticsearch:
149 # Array of hosts to connect to.
150 hosts: ["localhost:9200"]
151
152 # Optional protocol and basic auth credentials.
153 #protocol: "https"
154 #username: "elastic"
155 #password: "changeme"
156
157#----------------------------- Logstash output --------------------------------
158#output.logstash:
159 # The Logstash hosts
160 #hosts: ["localhost:5044"]
161
162 # Optional SSL. By default is off.
163 # List of root certificates for HTTPS server verifications
164 #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
165
166 # Certificate for SSL client authentication
167 #ssl.certificate: "/etc/pki/client/cert.pem"
168
169 # Client Certificate Key
170 #ssl.key: "/etc/pki/client/cert.key"
171
172#================================ Processors =====================================
173
174# Configure processors to enhance or manipulate events generated by the beat.
175
176processors:
177 - add_host_metadata: ~
178 - add_cloud_metadata: ~
179 - add_docker_metadata: ~
180 - add_kubernetes_metadata: ~
181
182#================================ Logging =====================================
183
184# Sets log level. The default log level is info.
185# Available log levels are: error, warning, info, debug
186#logging.level: debug
187
188# At debug level, you can selectively enable logging only for some components.
189# To enable all selectors use ["*"]. Examples of other selectors are "beat",
190# "publish", "service".
191#logging.selectors: ["*"]
192
193#============================== X-Pack Monitoring ===============================
194# filebeat can export internal metrics to a central Elasticsearch monitoring
195# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
196# reporting is disabled by default.
197
198# Set to true to enable the monitoring reporter.
199#monitoring.enabled: false
200
201# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
202# Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
203# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
204#monitoring.cluster_uuid:
205
206# Uncomment to send the metrics to Elasticsearch. Most settings from the
207# Elasticsearch output are accepted here as well.
208# Note that the settings should point to your Elasticsearch *monitoring* cluster.
209# Any setting that is not set is automatically inherited from the Elasticsearch
210# output configuration, so if you have the Elasticsearch output configured such
211# that it is pointing to your Elasticsearch monitoring cluster, you can simply
212# uncomment the following line.
213#monitoring.elasticsearch:
214
215#================================= Migration ==================================
216
217# This allows to enable 6.7 migration aliases
218#migration.6_to_7.enabled: true