# Heartbeat Down Counter

**URL:** https://discuss.elastic.co/t/heartbeat-down-counter/285817
**Category:** Kibana
**Created:** [October 4, 2021, 12:44pm UTC](https://discuss.elastic.co/t/heartbeat-down-counter/285817 "2021-10-04T12:44:32Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![maltewhiite](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maltewhiite/32/94551_2.png) [@maltewhiite](https://discuss.elastic.co/u/maltewhiite)
#### Post date: [October 4, 2021, 12:44pm UTC](https://discuss.elastic.co/t/heartbeat-down-counter/285817/1 "2021-10-04T12:44:32Z")

</div>

How do I make a simple counter, that show how many of my hosts are down?

We are running heartbeat.  
I'd think it was simple to make this, but I can't figure it out.

How do I make a simple counter that show how many of the lastest pings to hosts have returned "down"?

Or can I make a treemap or Donut or something, so I can also know which hosts those are.

This is probably really obvious, but I can't figure out how to make this. Seems like a common use-case.

EDIT: I just checked the server that is down, via Discover, and Heartbeat just stops checking the server when it dies? Then what is the point of Heartbeat? How do I then check if my servers are up or down? I thought that was the whole idea behind Heartbeat? Have I misunderstood something?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/6/a6446cff795bb2927387a79e0509318f0fe91440.png)

---

<div class="post-metadata">

### Author: ![maltewhiite](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maltewhiite/32/94551_2.png) [@maltewhiite](https://discuss.elastic.co/u/maltewhiite)
#### Post date: [October 21, 2021, 11:23am UTC](https://discuss.elastic.co/t/heartbeat-down-counter/285817/2 "2021-10-21T11:23:49Z")

</div>

What is the point of Heartbeat, if it stops logging, when the host dies? I thought it would then create logs that show that the host is down. Have I completely misunderstood something very fundamental here?

---

<div class="post-metadata">

### Author: ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)
#### Post date: [October 21, 2021, 3:16pm UTC](https://discuss.elastic.co/t/heartbeat-down-counter/285817/3 "2021-10-21T15:16:27Z")

</div>

The view in Observability \> Uptime should give you exactly what you want: [Uptime monitoring | Observability Guide [7.15] | Elastic](https://www.elastic.co/guide/en/observability/current/monitor-uptime.html)

It's difficult to re-build these views with the regular visualizations - Is there something specific missing in the uptime app for your case?

---

<div class="post-metadata">

### Author: ![maltewhiite](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maltewhiite/32/94551_2.png) [@maltewhiite](https://discuss.elastic.co/u/maltewhiite)
#### Post date: [October 22, 2021, 7:59am UTC](https://discuss.elastic.co/t/heartbeat-down-counter/285817/4 "2021-10-22T07:59:18Z")

</div>

Thank you Flash. I had indeed missed something very basic. I was trying to make that Observability \> Uptime page in a Custom Dashboard basically.

---

<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 19, 2021, 7:59am UTC](https://discuss.elastic.co/t/heartbeat-down-counter/285817/5 "2021-11-19T07:59:25Z")

</div>

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