Advertisement
Guest User

Untitled

a guest
Jul 25th, 2018
184
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.24 KB | None | 0 0
  1. ###################### Metricbeat Configuration Example #######################
  2.  
  3. # This file is an example configuration file highlighting only the most common
  4. # options. The metricbeat.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/metricbeat/index.html
  9.  
  10. #========================== Modules configuration ============================
  11.  
  12. metricbeat.config.modules:
  13.  
  14. # Glob pattern for configuration reloading
  15. path: C:/temp/Metricbeat/modules.d/*.yml
  16.  
  17. # Period on which files under path should be checked for changes
  18. reload.period: 10s
  19.  
  20. # Set to true to enable config reloading
  21. reload.enabled: false
  22.  
  23. # Maximum amount of time to randomly delay the start of a metricset. Use 0 to
  24. # disable startup delay.
  25. metricbeat.max_start_delay: 10s
  26.  
  27.  
  28.  
  29. metricbeat.modules:
  30. - module: system
  31. metricsets:
  32. - cpu
  33. - filesystem
  34. - memory
  35. - network
  36. - process
  37. enabled: true
  38. period: 10s
  39. processes: ['.*']
  40. cpu_ticks: false
  41. cpu.metrics: [percentages, normalized_percentages, ticks]
  42. #==================== Elasticsearch template setting ==========================
  43.  
  44. setup.template.settings:
  45. index.number_of_shards: 1
  46. index.codec: best_compression
  47. #_source.enabled: false
  48.  
  49. #================================ General =====================================
  50.  
  51. # The name of the shipper that publishes the network data. It can be used to group
  52. # all the transactions sent by a single shipper in the web interface.
  53. #name:
  54.  
  55. # The tags of the shipper are included in their own field with each
  56. # transaction published.
  57. #tags: ["service-X", "web-tier"]
  58.  
  59. # Optional fields that you can specify to add additional information to the
  60. # output.
  61. #fields:
  62. # env: staging
  63.  
  64.  
  65. #============================== Dashboards =====================================
  66. # These settings control loading the sample dashboards to the Kibana index. Loading
  67. # the dashboards is disabled by default and can be enabled either by setting the
  68. # options here, or by using the `-setup` CLI flag or the `setup` command.
  69. #setup.dashboards.enabled: false
  70.  
  71. # The URL from where to download the dashboards archive. By default this URL
  72. # has a value which is computed based on the Beat name and version. For released
  73. # versions, this URL points to the dashboard archive on the artifacts.elastic.co
  74. # website.
  75. #setup.dashboards.url:
  76.  
  77. #============================== Kibana =====================================
  78.  
  79. # Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
  80. # This requires a Kibana endpoint configuration.
  81. setup.kibana:
  82. hosts: ["localhost:5601"]
  83.  
  84. #============================= Elastic Cloud ==================================
  85.  
  86. # These settings simplify using metricbeat with the Elastic Cloud (https://cloud.elastic.co/).
  87.  
  88. # The cloud.id setting overwrites the `output.elasticsearch.hosts` and
  89. # `setup.kibana.host` options.
  90. # You can find the `cloud.id` in the Elastic Cloud web UI.
  91. #cloud.id:
  92.  
  93. # The cloud.auth setting overwrites the `output.elasticsearch.username` and
  94. # `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
  95. #cloud.auth:
  96.  
  97. #================================ Outputs =====================================
  98.  
  99. # Configure what output to use when sending the data collected by the beat.
  100.  
  101. #-------------------------- Elasticsearch output ------------------------------
  102. output.elasticsearch:
  103. # Array of hosts to connect to.
  104. hosts: ["localhost:9200"]
  105. username: "elastic"
  106. password: "changeme"
  107.  
  108. #----------------------------- Logstash output --------------------------------
  109. #output.logstash:
  110. # The Logstash hosts
  111. #hosts: ["localhost:5044"]
  112.  
  113. # Optional SSL. By default is off.
  114. # List of root certificates for HTTPS server verifications
  115. #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
  116.  
  117. # Certificate for SSL client authentication
  118. #ssl.certificate: "/etc/pki/client/cert.pem"
  119.  
  120. # Client Certificate Key
  121. #ssl.key: "/etc/pki/client/cert.key"
  122.  
  123. #================================ Logging =====================================
  124.  
  125. # Sets log level. The default log level is info.
  126. # Available log levels are: error, warning, info, debug
  127. #logging.level: debug
  128.  
  129. # At debug level, you can selectively enable logging only for some components.
  130. # To enable all selectors use ["*"]. Examples of other selectors are "beat",
  131. # "publish", "service".
  132. #logging.selectors: ["*"]
  133.  
  134. #============================== Xpack Monitoring ===============================
  135. # metricbeat can export internal metrics to a central Elasticsearch monitoring
  136. # cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
  137. # reporting is disabled by default.
  138.  
  139. # Set to true to enable the monitoring reporter.
  140. #xpack.monitoring.enabled: false
  141.  
  142. # Uncomment to send the metrics to Elasticsearch. Most settings from the
  143. # Elasticsearch output are accepted here as well. Any setting that is not set is
  144. # automatically inherited from the Elasticsearch output configuration, so if you
  145. # have the Elasticsearch output configured, you can simply uncomment the
  146. # following line.
  147. #xpack.monitoring.elasticsearch:
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement