# Trying to get some more throughput from Winlogbeat **URL:** \ **Category:** Beats\ **Tags:** winlogbeat\ **Created:** [January 8, 2018, 7:55pm UTC](https://discuss.elastic.co/t/trying-to-get-some-more-throughput-from-winlogbeat/114606 "2018-01-08T19:55:49Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![John\_Schoonover](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_schoonover/32/135347_2.png) [@John\_Schoonover](https://discuss.elastic.co/u/John_Schoonover)\ **Post date:** [January 8, 2018, 7:55pm UTC](https://discuss.elastic.co/t/trying-to-get-some-more-throughput-from-winlogbeat/114606/1 "2018-01-08T19:55:49Z")
Hey all: I've recently installed Winlogbeat [5.6] to a server and am trying to increase throughput. It seems that I'm unable to get it to send \>300 events per second (as evidenced by my ELK monitoring cluster looking at the indexing rate). Any unique configurations I can look into to enable better throughput? I've verified resource availability on both the Logstash & Host Server side. Thanks, John ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [January 8, 2018, 8:24pm UTC](https://discuss.elastic.co/t/trying-to-get-some-more-throughput-from-winlogbeat/114606/2 "2018-01-08T20:24:15Z")
The first thing I recommend is trying the latest Winlogbeat 6.1 release. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 5, 2018, 8:24pm UTC](https://discuss.elastic.co/t/trying-to-get-some-more-throughput-from-winlogbeat/114606/3 "2018-02-05T20:24:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.