daily pastebin goal
50%
SHARE
TWEET

Untitled

a guest Nov 5th, 2018 374 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. ###################### Winlogbeat Configuration Example ##########################
  2.  
  3. # This file is an example configuration file highlighting only the most common
  4. # options. The winlogbeat.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/winlogbeat/index.html
  9.  
  10. #======================= Winlogbeat specific options ==========================
  11.  
  12. # event_logs specifies a list of event logs to monitor as well as any
  13. # accompanying options. The YAML data type of event_logs is a list of
  14. # dictionaries.
  15. #
  16. # The supported keys are name (required), tags, fields, fields_under_root,
  17. # forwarded, ignore_older, level, event_id, provider, and include_xml. Please
  18. # visit the documentation for the complete details of each option.
  19. # https://go.es.io/WinlogbeatConfig
  20. winlogbeat.event_logs:
  21.   - name: Application
  22.     ignore_older: 72h
  23.   - name: Security
  24.   - name: System
  25.  
  26. #==================== Elasticsearch template setting ==========================
  27.  
  28. #setup.template.settings:
  29. #  index.number_of_shards: 3
  30.   #index.codec: best_compression
  31.   #_source.enabled: false
  32.  
  33. #================================ General =====================================
  34.  
  35. # The name of the shipper that publishes the network data. It can be used to group
  36. # all the transactions sent by a single shipper in the web interface.
  37. #name:
  38.  
  39. # The tags of the shipper are included in their own field with each
  40. # transaction published.
  41. #tags: ["service-X", "web-tier"]
  42.  
  43. # Optional fields that you can specify to add additional information to the
  44. # output.
  45. #fields:
  46. #  env: staging
  47.  
  48.  
  49. #============================== Dashboards =====================================
  50. # These settings control loading the sample dashboards to the Kibana index. Loading
  51. # the dashboards is disabled by default and can be enabled either by setting the
  52. # options here, or by using the `-setup` CLI flag or the `setup` command.
  53. #setup.dashboards.enabled: false
  54.  
  55. # The URL from where to download the dashboards archive. By default this URL
  56. # has a value which is computed based on the Beat name and version. For released
  57. # versions, this URL points to the dashboard archive on the artifacts.elastic.co
  58. # website.
  59. #setup.dashboards.url:
  60.  
  61. #============================== Kibana =====================================
  62.  
  63. # Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
  64. # This requires a Kibana endpoint configuration.
  65. #setup.kibana:
  66.  
  67.   # Kibana Host
  68.   # Scheme and port can be left out and will be set to the default (http and 5601)
  69.   # In case you specify and additional path, the scheme is required: http://localhost:5601/path
  70.   # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  71.   #host: "localhost:5601"
  72.  
  73. #============================= Elastic Cloud ==================================
  74.  
  75. # These settings simplify using winlogbeat with the Elastic Cloud (https://cloud.elastic.co/).
  76.  
  77. # The cloud.id setting overwrites the `output.elasticsearch.hosts` and
  78. # `setup.kibana.host` options.
  79. # You can find the `cloud.id` in the Elastic Cloud web UI.
  80. #cloud.id:
  81.  
  82. # The cloud.auth setting overwrites the `output.elasticsearch.username` and
  83. # `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
  84. #cloud.auth:
  85.  
  86. #================================ Outputs =====================================
  87.  
  88. # Configure what output to use when sending the data collected by the beat.
  89.  
  90. #-------------------------- Elasticsearch output ------------------------------
  91. #output.elasticsearch:
  92.   # Array of hosts to connect to.
  93.   #hosts: ["localhost:9200"]
  94.  
  95.   # Optional protocol and basic auth credentials.
  96.   #protocol: "https"
  97.   #username: "elastic"
  98.   #password: "changeme"
  99.  
  100. #----------------------------- Logstash output --------------------------------
  101. #output.logstash:
  102.   # The Logstash hosts
  103.   #hosts: ["localhost:5044"]
  104.  
  105.   # Optional SSL. By default is off.
  106.   # List of root certificates for HTTPS server verifications
  107.   #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
  108.  
  109.   # Certificate for SSL client authentication
  110.   #ssl.certificate: "/etc/pki/client/cert.pem"
  111.  
  112.   # Client Certificate Key
  113.   #ssl.key: "/etc/pki/client/cert.key"
  114.  
  115. #================================ Logging =====================================
  116.  
  117. # Sets log level. The default log level is info.
  118. # Available log levels are: error, warning, info, debug
  119. #logging.level: debug
  120.  
  121. # At debug level, you can selectively enable logging only for some components.
  122. # To enable all selectors use ["*"]. Examples of other selectors are "beat",
  123. # "publish", "service".
  124. #logging.selectors: ["*"]
  125.  
  126. #============================== Xpack Monitoring ===============================
  127. # winlogbeat can export internal metrics to a central Elasticsearch monitoring
  128. # cluster.  This requires xpack monitoring to be enabled in Elasticsearch.  The
  129. # reporting is disabled by default.
  130.  
  131. # Set to true to enable the monitoring reporter.
  132. #xpack.monitoring.enabled: false
  133.  
  134. # Uncomment to send the metrics to Elasticsearch. Most settings from the
  135. # Elasticsearch output are accepted here as well. Any setting that is not set is
  136. # automatically inherited from the Elasticsearch output configuration, so if you
  137. # have the Elasticsearch output configured, you can simply uncomment the
  138. # following line.
  139. #xpack.monitoring.elasticsearch:
  140.  
  141.  
  142. fields:
  143.   logzio_codec: json
  144.   token: 4c92540f-0e29-4451-8418-495c39114d7b
  145. fields_under_root: true
  146.  
  147. output.logstash:
  148.   hosts: ["listener.logz.io:5015"]
  149.   ssl.certificate_authorities: ['C:\winlogbeat\Logzio.crt']
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top