# Ping input plugin for logstash

**URL:** <https://discuss.elastic.co/t/ping-input-plugin-for-logstash/107717>\
**Category:** Logstash\
**Created:** [November 15, 2017, 10:12am UTC](https://discuss.elastic.co/t/ping-input-plugin-for-logstash/107717 "2017-11-15T10:12:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidecavestro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidecavestro/32/23461_2.png) [@davidecavestro](https://discuss.elastic.co/u/davidecavestro)\
**Post date:** [November 15, 2017, 10:12am UTC](https://discuss.elastic.co/t/ping-input-plugin-for-logstash/107717/1 "2017-11-15T10:12:30Z")

</div>

I've just published [logstash-input-ping](https://rubygems.org/gems/logstash-input-ping).

It is meant to acquire ping metrics directly from logstash: the same can be done using PingBeat or other stuff...  
in fact I did it just to learn some ruby 🙂

However if there's some interest I can further enhance it.  
i.e. exposing some way to fine tune the probes used at lower level by the _net-ping_ library or exposing a one shot mode, as currently it continuously produces data in loop-with-sleep or scheduled mode.

The project is hosted at [https://github.com/davidecavestro/logstash-input-ping](https://github.com/davidecavestro/logstash-input-ping)

---

<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:** [December 13, 2017, 10:13am UTC](https://discuss.elastic.co/t/ping-input-plugin-for-logstash/107717/2 "2017-12-13T10:13:10Z")

</div>

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