# 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:** 13
**Page:** 1
### Author:  [@MichaelScofield](https://discuss.elastic.co/u/MichaelScofield)
#### Post date: [August 11, 2015, 5:23am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/1 "2015-08-11T05:23:40Z")
Are there any tools that can monitor logstash's health? I googled it but found no answers.
---
### Author:  [@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")
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β¦
---
### Author:  [@MichaelScofield](https://discuss.elastic.co/u/MichaelScofield)
#### Post date: [August 11, 2015, 5:47am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/3 "2015-08-11T05:47:13Z")
Thanks! That discussion is enlightening. However, I am looking for some metrics like "how many events are received/sent per second" or "how many bytes are received/sent per second".
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [August 11, 2015, 5:55am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/4 "2015-08-11T05:55:37Z")
Well, if you run statsd you can have Logstash ping it for each message and you'll at least get events/s.
---
### Author:  [@MichaelScofield](https://discuss.elastic.co/u/MichaelScofield)
#### Post date: [August 11, 2015, 6:27am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/5 "2015-08-11T06:27:14Z")
Thanks for the reply, but I'm not very clear about how to "ping" the statsd.
Do you mean that I have to include the statsd output plugin and have it feed with some event field like timestamp?
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [August 11, 2015, 6:32am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/6 "2015-08-11T06:32:25Z")
> Do you mean that I have to include the statsd output plugin and have it feed with some event field like timestamp?
Not the timestamp since that's implied but you could send metrics to a counter-type metric named logstash.events or whatever you want, and stastd will periodically emit both the absolute count and the rate.
---
### Author:  [@MichaelScofield](https://discuss.elastic.co/u/MichaelScofield)
#### Post date: [August 11, 2015, 6:36am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/7 "2015-08-11T06:36:23Z")
Ah, thanks! π
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [August 11, 2015, 10:21am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/8 "2015-08-11T10:21:31Z")
LS 2.0 will have this sort of thing exposed π
---
### Author:  [@MichaelScofield](https://discuss.elastic.co/u/MichaelScofield)
#### Post date: [August 11, 2015, 10:25am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/9 "2015-08-11T10:25:18Z")
Thx! Really looking forward to 2.0, it's better to have these kinds of metrics got from logstash itself.
Is there any plan releasing 2.0?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [August 11, 2015, 10:35am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/10 "2015-08-11T10:35:24Z")
I'm not sure of the timeline on that one sorry.
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [August 13, 2015, 4:41pm UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/11 "2015-08-13T16:41:58Z")
@MichaelScofield we're still working on figuring out the timeline at the moment. There will def be an announcement when we have one however!
---
### Author:  [@m1k3ga](https://discuss.elastic.co/u/m1k3ga)
#### Post date: [August 14, 2015, 7:44am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/12 "2015-08-14T07:44:45Z")
According to the statsd doc it uses the %{host} field as logging host.
In our setup with many logstash shippers and indexers the host is always the name of the original host where the logfile was read from.
**How** do you distinguish between each instance for monitoring each logstash instance?
We use the metrics plugin with environment plugin ($HOSTNAME) to trigger a heartbeat event from each logstash instance every 60 seconds.
But statsd seems to be interesting, i will have a look at it.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 5:31am UTC](https://discuss.elastic.co/t/how-to-monitor-logstash-itself/27172/13 "2017-07-06T05:31:59Z")