# Comparison of heartbeat and zabbix

**URL:** <https://discuss.elastic.co/t/comparison-of-heartbeat-and-zabbix/152002>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [October 11, 2018, 7:53am UTC](https://discuss.elastic.co/t/comparison-of-heartbeat-and-zabbix/152002 "2018-10-11T07:53:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mukai](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@mukai](https://discuss.elastic.co/u/mukai)\
**Post date:** [October 11, 2018, 7:53am UTC](https://discuss.elastic.co/t/comparison-of-heartbeat-and-zabbix/152002/1 "2018-10-11T07:53:54Z")

</div>

I want to use Heartbeat in our office.  
Heartbeat is very easy to use and lightweight.

However, there is already Zabbix in the office.  
What are the strengths of Heartbeat?

(URL) Heartbeat  
[https://www.elastic.co/products/beats/heartbeat](https://www.elastic.co/products/beats/heartbeat)  
(URL) Zabbix  
[https://www.zabbix.com/whats\_new](https://www.zabbix.com/whats_new)

---

<div class="post-metadata">

**Author:** ![dov0211](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dov0211/32/36505_2.png) [@dov0211](https://discuss.elastic.co/u/dov0211)\
**Post date:** [October 12, 2018, 11:33am UTC](https://discuss.elastic.co/t/comparison-of-heartbeat-and-zabbix/152002/2 "2018-10-12T11:33:20Z")

</div>

Hello,  
There are several differences between Heartbeat and Zabbix with respect for "uptime monitoring"  
One of the main difference is that in Zabbix there is no dedicated agent that is doing the checks for you, the checks are been executed from Zabbix-server itself, meaning that you must provide an access from Zabbix server to your end point which you would like to check.

Heartbeat (similar to our other beats) is a lightweight shipper, which can be installed practically anywhere (in or outside your network) and target a specific use case, which is "uptime monitoring".  
Heartbeat can monitor both internal and external endpoints and provide you with the information if those end-points or services are up and running.  
.  
Heartbeat provides HTTP/S ICMP and TCP checks, it can do body checks, it then sends all the information to the elasticsearch, where there you can leverage the full power of the stack (visualizations, alerting and more...)

in addition you can deploy multiple heartbeats in different locations and monitor the same endpoint/service to get a wide perspective on your service accessibility from various locations.

---

<div class="post-metadata">

**Author:** ![mukai](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@mukai](https://discuss.elastic.co/u/mukai)\
**Post date:** [October 17, 2018, 5:20am UTC](https://discuss.elastic.co/t/comparison-of-heartbeat-and-zabbix/152002/3 "2018-10-17T05:20:37Z")

</div>

Thank you for your answer.

I didn’t know about the difference before, but now I know well.

> in addition you can deploy multiple heartbeats in different locations and monitor the same endpoint/service to get a wide perspective on your service accessibility from various locations.

I think it is particularly attractive that I can deploy multiple heartbeats in different location.  
I will try using heartbeat at my office.

Thank you very much.

---

<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 14, 2018, 5:26am UTC](https://discuss.elastic.co/t/comparison-of-heartbeat-and-zabbix/152002/4 "2018-11-14T05:26:34Z")

</div>

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