# ZeroMQ connectivity-check

**URL:** <https://discuss.elastic.co/t/zeromq-connectivity-check/27259>\
**Category:** Logstash\
**Created:** [August 12, 2015, 1:29pm UTC](https://discuss.elastic.co/t/zeromq-connectivity-check/27259 "2015-08-12T13:29:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eru](https://avatars.discourse-cdn.com/v4/letter/e/48db29/32.png) [@Eru](https://discuss.elastic.co/u/Eru)\
**Post date:** [August 12, 2015, 1:29pm UTC](https://discuss.elastic.co/t/zeromq-connectivity-check/27259/1 "2015-08-12T13:29:36Z")

</div>

Hi,

We are using ELK in production, and some apps are shipping to logtash via ZeroQM and files..  
Occasionally our servers go offline, and sometimes logstash can't boot-up properly.  
We have a fallback that ships the logs via files, but it's disabled by default.  
We would like to find a way to check with the logstash-server that it is alive, and if not getting a response, then reactivate the fallback to file-shipping immediately, so we don't loose any logs.  
Is there an easy way to configure logstash with this kind of check?  
Perhaps using a specific topology on another input that echoes something back?

Any tips would be appreciated 😄

---

<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:** [July 6, 2017, 5:32am UTC](https://discuss.elastic.co/t/zeromq-connectivity-check/27259/2 "2017-07-06T05:32:11Z")

</div>


