Advertisement
Guest User

Untitled

a guest
Sep 13th, 2018
116
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.34 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 inputs =============================
  14.  
  15. filebeat.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: true
  25.  
  26. # Paths that should be crawled and fetched. Glob based paths.
  27. paths:
  28. - /home/tsamusev/coral/helm-api/*.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.  
  68. filebeat.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.  
  80. setup.template.name: "filebeat"
  81. setup.template.pattern: "filebeat-*"
  82.  
  83. setup.template.settings:
  84. index.number_of_shards: 3
  85. #index.codec: best_compression
  86. #_source.enabled: false
  87.  
  88. #================================ General =====================================
  89.  
  90. # The name of the shipper that publishes the network data. It can be used to group
  91. # all the transactions sent by a single shipper in the web interface.
  92. #name:
  93.  
  94. # The tags of the shipper are included in their own field with each
  95. # transaction published.
  96. #tags: ["service-X", "web-tier"]
  97.  
  98. # Optional fields that you can specify to add additional information to the
  99. # output.
  100. #fields:
  101. # env: staging
  102.  
  103.  
  104. #============================== Dashboards =====================================
  105. # These settings control loading the sample dashboards to the Kibana index. Loading
  106. # the dashboards is disabled by default and can be enabled either by setting the
  107. # options here, or by using the `-setup` CLI flag or the `setup` command.
  108. #setup.dashboards.enabled: false
  109.  
  110. # The URL from where to download the dashboards archive. By default this URL
  111. # has a value which is computed based on the Beat name and version. For released
  112. # versions, this URL points to the dashboard archive on the artifacts.elastic.co
  113. # website.
  114. #setup.dashboards.url:
  115.  
  116. #============================== Kibana =====================================
  117.  
  118. # Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
  119. # This requires a Kibana endpoint configuration.
  120. #setup.kibana:
  121.  
  122. # Kibana Host
  123. # Scheme and port can be left out and will be set to the default (http and 5601)
  124. # In case you specify and additional path, the scheme is required: http://localhost:5601/path
  125. # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  126. # host: "localhost:5601"
  127.  
  128. #============================= Elastic Cloud ==================================
  129.  
  130. # These settings simplify using filebeat with the Elastic Cloud (https://cloud.elastic.co/).
  131.  
  132. # The cloud.id setting overwrites the `output.elasticsearch.hosts` and
  133. # `setup.kibana.host` options.
  134. # You can find the `cloud.id` in the Elastic Cloud web UI.
  135. #cloud.id:
  136.  
  137. # The cloud.auth setting overwrites the `output.elasticsearch.username` and
  138. # `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
  139. #cloud.auth:
  140.  
  141. #================================ Outputs =====================================
  142.  
  143. # Configure what output to use when sending the data collected by the beat.
  144.  
  145. #-------------------------- Elasticsearch output ------------------------------
  146. #output.elasticsearch:
  147. # Array of hosts to connect to.
  148. # hosts: ["localhost:9200"]
  149.  
  150. # Optional protocol and basic auth credentials.
  151. #protocol: "https"
  152. #username: "elastic"
  153. #password: "changeme"
  154.  
  155. #----------------------------- Logstash output --------------------------------
  156. output.logstash:
  157. # The Logstash hosts
  158. hosts: ["localhost:5044"]
  159.  
  160. # Optional SSL. By default is off.
  161. # List of root certificates for HTTPS server verifications
  162. #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
  163.  
  164. # Certificate for SSL client authentication
  165. #ssl.certificate: "/etc/pki/client/cert.pem"
  166.  
  167. # Client Certificate Key
  168. #ssl.key: "/etc/pki/client/cert.key"
  169.  
  170. #================================ Logging =====================================
  171.  
  172. # Sets log level. The default log level is info.
  173. # Available log levels are: error, warning, info, debug
  174. #logging.level: debug
  175.  
  176. # At debug level, you can selectively enable logging only for some components.
  177. # To enable all selectors use ["*"]. Examples of other selectors are "beat",
  178. # "publish", "service".
  179. #logging.selectors: ["*"]
  180.  
  181. #============================== Xpack Monitoring ===============================
  182. # filebeat can export internal metrics to a central Elasticsearch monitoring
  183. # cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
  184. # reporting is disabled by default.
  185.  
  186. # Set to true to enable the monitoring reporter.
  187. #xpack.monitoring.enabled: false
  188.  
  189. # Uncomment to send the metrics to Elasticsearch. Most settings from the
  190. # Elasticsearch output are accepted here as well. Any setting that is not set is
  191. # automatically inherited from the Elasticsearch output configuration, so if you
  192. # have the Elasticsearch output configured, you can simply uncomment the
  193. # following line.
  194. #xpack.monitoring.elasticsearch:
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement