# Node Up / Down Monitoring

**URL:** https://discuss.elastic.co/t/node-up-down-monitoring/64948
**Category:** Beats
**Created:** [November 3, 2016, 8:50pm UTC](https://discuss.elastic.co/t/node-up-down-monitoring/64948 "2016-11-03T20:50:23Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![seth.yes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seth.yes/32/11788_2.png) [@seth.yes](https://discuss.elastic.co/u/seth.yes)
#### Post date: [November 3, 2016, 8:50pm UTC](https://discuss.elastic.co/t/node-up-down-monitoring/64948/1 "2016-11-03T20:50:23Z")

</div>

I'm with a team that is migrating our monitoring stack to open source. I've implemented some fantastic performance and service-specific monitoring using the ELK stack.

One key monitor I need to implement which isn't exactly straightforward is simple node Up/Down monitoring. I've got this working down to a service-specific level by using Nmap to write to a file which I tail with Filebeat  
(e.g. `nmap mapsmysql01 | grep mysql >> /var/log/alerts/mysqlup.log`)

However, I must intermittently check that both mysql is down and filebeat is up before throwing an alert.

Is there a more elegant way to monitor service or node up/down? I imagine I'm missing something here..

---

<div class="post-metadata">

### Author: ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)
#### Post date: [November 3, 2016, 9:26pm UTC](https://discuss.elastic.co/t/node-up-down-monitoring/64948/2 "2016-11-03T21:26:01Z")

</div>

[Heartbeat](https://github.com/elastic/beats/tree/master/heartbeat) ([snapshots](https://beats-nightlies.s3.amazonaws.com/index.html?prefix=heartbeat/) ) might be of interest to you. It's a new Beat we are working on to monitor availability.

It doesn't have docs yet and it's not released. Have a look at the config file and readme.

---

<div class="post-metadata">

### Author: ![seth.yes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seth.yes/32/11788_2.png) [@seth.yes](https://discuss.elastic.co/u/seth.yes)
#### Post date: [November 3, 2016, 10:25pm UTC](https://discuss.elastic.co/t/node-up-down-monitoring/64948/3 "2016-11-03T22:25:27Z")

</div>

Thanks @andrewkroh, that looks like precisely what I was hoping for.

---

<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: [November 24, 2016, 8:50pm UTC](https://discuss.elastic.co/t/node-up-down-monitoring/64948/4 "2016-11-24T20:50:36Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.
