# Any tips for monitoring Logstash performance
**URL:** https://discuss.elastic.co/t/any-tips-for-monitoring-logstash-performance/1004
**Category:** Logstash
**Created:** [May 20, 2015, 5:07pm UTC](https://discuss.elastic.co/t/any-tips-for-monitoring-logstash-performance/1004 "2015-05-20T17:07:37Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@madCow](https://discuss.elastic.co/u/madCow)
#### Post date: [May 20, 2015, 5:07pm UTC](https://discuss.elastic.co/t/any-tips-for-monitoring-logstash-performance/1004/1 "2015-05-20T17:07:37Z")
Hi,
I have a simple ELK stack at present which looks to be working fine. I'm running on a single machine and getting around 60 messages every 5 mins and plan to double that soon. Can some more experienced users recommend some steps I can take to monitor the performance?
I can see basic machine stats but that seems quite broad. I believe Logstash uses queues internally, can I see if I'm overloading them perhaps? Am I about to run out of Java memory or some such? do I need more workers to scale?
I send most of my traffic to Logstash via the udp plugin, so it could be ignoring a lot of traffic I may not know.
Any advice to keep my setup running smoothly is welcome.
Regards
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [May 20, 2015, 11:35pm UTC](https://discuss.elastic.co/t/any-tips-for-monitoring-logstash-performance/1004/2 "2015-05-20T23:35:13Z")
Monitoring in LS is very basic at the moment as we don't expose anything internally, including the queue.
You could look at using the [metrics filter](https://www.elastic.co/guide/en/logstash/current/plugins-filters-metrics.html) to do something at a high level.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 5:39am UTC](https://discuss.elastic.co/t/any-tips-for-monitoring-logstash-performance/1004/3 "2017-07-06T05:39:33Z")