# Custom monitoring of ELK

**URL:** <https://discuss.elastic.co/t/custom-monitoring-of-elk/98857>\
**Category:** Kibana\
**Created:** [August 30, 2017, 1:39pm UTC](https://discuss.elastic.co/t/custom-monitoring-of-elk/98857 "2017-08-30T13:39:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nh45](https://avatars.discourse-cdn.com/v4/letter/n/c0e974/32.png) [@nh45](https://discuss.elastic.co/u/nh45)\
**Post date:** [August 30, 2017, 1:39pm UTC](https://discuss.elastic.co/t/custom-monitoring-of-elk/98857/1 "2017-08-30T13:39:16Z")

</div>

Hi,

Although Kibana monitoring is superb for visualization of current ELK stats. What we need is a nice way of aggregating these numbers so that we can get early alerts of critical disk space, memory, cpu for each of the cluster nodes. Are there any tools available that will deliver these stats? or is there some way of developing some custom queries/scripts?

---

<div class="post-metadata">

**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\
**Post date:** [August 30, 2017, 3:50pm UTC](https://discuss.elastic.co/t/custom-monitoring-of-elk/98857/2 "2017-08-30T15:50:07Z")

</div>

Hi @nh45,

X-Pack includes an [alerting](https://www.elastic.co/products/x-pack/alerting) feature, that can notify people and other systems when specific conditions in Elasticsearch are fulfilled. Since the monitoring data are stored as Elasticsearch documents, they can be used as a basis for alerts too. Currently this requires manual creation of the appropriate alerts, but providing more convenient user interfaces for creating alerts based on monitoring data is something we are working on. There are also 3rd-party solutions for alerting based on Elasticsearch (e.g. [https://github.com/Yelp/elastalert](https://github.com/Yelp/elastalert)), which require running additional services in the infrastructure.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 30, 2017, 9:38pm UTC](https://discuss.elastic.co/t/custom-monitoring-of-elk/98857/3 "2017-08-30T21:38:18Z")

</div>

FYI we’ve renamed ELK to the Elastic Stack, otherwise Beats feels left out 😉

---

<div class="post-metadata">

**Author:** ![nh45](https://avatars.discourse-cdn.com/v4/letter/n/c0e974/32.png) [@nh45](https://discuss.elastic.co/u/nh45)\
**Post date:** [August 31, 2017, 8:46am UTC](https://discuss.elastic.co/t/custom-monitoring-of-elk/98857/4 "2017-08-31T08:46:59Z")

</div>

@warkolm thanks for info' will try to re-educate myself and my team members.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 28, 2017, 8:47am UTC](https://discuss.elastic.co/t/custom-monitoring-of-elk/98857/5 "2017-09-28T08:47:04Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.