Parth6288

filebeat.yml

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