2017-11-02 12:25:10 -04:00
|
|
|
|
[role="xpack"]
|
|
|
|
|
|
[[es-monitoring]]
|
|
|
|
|
|
= Monitoring {es}
|
|
|
|
|
|
|
|
|
|
|
|
[partintro]
|
|
|
|
|
|
--
|
|
|
|
|
|
{monitoring} enables you to easily monitor the health of your {es} cluster. The
|
2018-02-23 11:23:16 -05:00
|
|
|
|
monitoring metrics are collected from each node and stored in {es} indices.
|
|
|
|
|
|
|
|
|
|
|
|
Each {es} node is considered unique based on its persistent UUID, which is
|
|
|
|
|
|
written on first start to its <<path-settings,`path.data`>> directory, which
|
|
|
|
|
|
defaults to `./data`.
|
|
|
|
|
|
|
|
|
|
|
|
You can view the monitoring data from {kib} where it’s easy to spot issues at a
|
|
|
|
|
|
glance or delve into the system behavior over time to diagnose operational
|
|
|
|
|
|
issues. In addition to the built-in status warnings, you can also set up custom
|
|
|
|
|
|
alerts based on the data in the monitoring indices.
|
2017-11-02 12:25:10 -04:00
|
|
|
|
|
|
|
|
|
|
This section focuses on the {es} monitoring infrastructure and setup. For an
|
|
|
|
|
|
introduction to monitoring your Elastic stack, including Logstash and {kib}, see
|
|
|
|
|
|
{xpack-ref}/xpack-monitoring.html[Monitoring the Elastic Stack].
|
2018-02-23 11:23:16 -05:00
|
|
|
|
|
|
|
|
|
|
* <<configuring-monitoring>>
|
2018-03-19 19:48:07 -04:00
|
|
|
|
* <<es-monitoring-overview>>
|
2018-02-23 11:23:16 -05:00
|
|
|
|
* <<stats-export>>
|
|
|
|
|
|
* <<http-exporter>>
|
2017-11-02 12:25:10 -04:00
|
|
|
|
|
|
|
|
|
|
--
|
|
|
|
|
|
|
2018-03-19 19:48:07 -04:00
|
|
|
|
include::overview.asciidoc[]
|
2017-11-02 12:25:10 -04:00
|
|
|
|
include::stats-export.asciidoc[]
|
|
|
|
|
|
include::http-export.asciidoc[]
|
