# How to monitor logstash itself?

**URL:** https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172
**Category:** Logstash
**Created:** [August 11, 2015, 5:23am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172 "2015-08-11T05:23:40Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [August 11, 2015, 5:27am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/2 "2015-08-11T05:27:24Z")

</div>

The following discussion from a day or two ago might be helpful. If not, please be more specific in what you're after.

> [@How to get alerts for logstash failures of plugins / input / filters?](https://discuss.elastic.co/t/how-to-get-alerts-for-logstash-failures-of-plugins-input-filters/27087):
>
> Inside logstash, what is the official mechanism to know about any critical errors that happen with plugins / inputs / filters during the production run? For example, I am using http\_poller input and elastic output. Say, if for some reason the http\_poller is unable to read the input properly from the url or elastic unable to save the output - is there anyway I can configure logstash to send me alert mails ? Generating debug / stdout errors to console would not help in backend systems case - rig…

---

_[View the full topic](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172)._