Advertisement
Guest User

filebeat.yml

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