# Setting \`congestion\_threshold\` in plugin \`beats\` --getting below error any solution to fix this

**URL:** <https://discuss.elastic.co/t/setting-congestion-threshold-in-plugin-beats-getting-below-error-any-solution-to-fix-this/166853>\
**Category:** Logstash\
**Created:** [February 3, 2019, 6:33am UTC](https://discuss.elastic.co/t/setting-congestion-threshold-in-plugin-beats-getting-below-error-any-solution-to-fix-this/166853 "2019-02-03T06:33:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rajesh123vit](https://avatars.discourse-cdn.com/v4/letter/r/ee7513/32.png) [@rajesh123vit](https://discuss.elastic.co/u/rajesh123vit)\
**Post date:** [February 3, 2019, 6:33am UTC](https://discuss.elastic.co/t/setting-congestion-threshold-in-plugin-beats-getting-below-error-any-solution-to-fix-this/166853/1 "2019-02-03T06:33:07Z")

</div>

sudo -u logstash /usr/share/logstash/bin/logstash --path.settings /etc/logstash -t

Sending Logstash logs to /var/log/logstash which is now configured via log4j2.properties  
[2019-02-03T11:55:15,766][FATAL][logstash.runner] The given configuration is invalid. Reason: The setting `congestion_threshold` in plugin `beats` is obsolete and is no longer available. This option is obsolete since congestion control is done automatically If you have any questions about this, you are invited to visit [https://discuss.elastic.co/c/logstash](https://discuss.elastic.co/c/logstash) and ask.  
[2019-02-03T11:55:15,811][ERROR][org.logstash.Logstash] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) ex

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [February 3, 2019, 12:59pm UTC](https://discuss.elastic.co/t/setting-congestion-threshold-in-plugin-beats-getting-below-error-any-solution-to-fix-this/166853/2 "2019-02-03T12:59:18Z")

</div>

You have specified 'congestion\_threshold =\> someNumber' in the configuration of your beats input. You should remove it because the option is obsolete.

---

<div class="post-metadata">

**Author:** ![rajesh123vit](https://avatars.discourse-cdn.com/v4/letter/r/ee7513/32.png) [@rajesh123vit](https://discuss.elastic.co/u/rajesh123vit)\
**Post date:** [February 3, 2019, 5:17pm UTC](https://discuss.elastic.co/t/setting-congestion-threshold-in-plugin-beats-getting-below-error-any-solution-to-fix-this/166853/3 "2019-02-03T17:17:11Z")

</div>

> [@Badger](#):
>
> congestion\_threshold

After removing 'congestion\_threshold =\> someNumber' in the configuration  
getting following error  
Sending Logstash logs to /var/log/logstash which is now configured via log4j2.properties  
[2019-02-03T22:42:54,106][ERROR][logstash.inputs.beats] Unknown setting 'congestion\_threshold' for beats  
[2019-02-03T22:42:54,188][FATAL][logstash.runner] The given configuration is invalid. Reason: Something is wrong with your configuration.  
[2019-02-03T22:42:54,217][ERROR][org.logstash.Logstash] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [February 3, 2019, 5:29pm UTC](https://discuss.elastic.co/t/setting-congestion-threshold-in-plugin-beats-getting-below-error-any-solution-to-fix-this/166853/4 "2019-02-03T17:29:41Z")

</div>

Can you show us the configuration of your input?

---

<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:** [March 3, 2019, 5:29pm UTC](https://discuss.elastic.co/t/setting-congestion-threshold-in-plugin-beats-getting-below-error-any-solution-to-fix-this/166853/5 "2019-03-03T17:29:41Z")

</div>

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