# How can I identify back pressure in logstash

**URL:** https://discuss.elastic.co/t/how-can-i-identify-back-pressure-in-logstash/157581
**Category:** Logstash
**Created:** [November 20, 2018, 4:04pm UTC](https://discuss.elastic.co/t/how-can-i-identify-back-pressure-in-logstash/157581 "2018-11-20T16:04:40Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![meetdave2611997](https://avatars.discourse-cdn.com/v4/letter/m/f07891/32.png) [@meetdave2611997](https://discuss.elastic.co/u/meetdave2611997)
#### Post date: [November 20, 2018, 4:04pm UTC](https://discuss.elastic.co/t/how-can-i-identify-back-pressure-in-logstash/157581/1 "2018-11-20T16:04:40Z")

</div>

Hi,

we are trying to create some alerting in elasticsearch side which would notify us when logstash puts back pressure on inputs and stops accepting data. we are currently using three types of inputs: beats, tcp and http.

In our environment, beats are sending data to logstash and logstash then ships it to elasticsearch. Can we have second filebeat which would only monitor primary filebeat logs and ships each errors produced by primary filebeat directly to Elasticsearch so that we can search for `i/o read timeout` errors in primary filebeat. Is this feasible solution?

Thanks

---

<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: [December 18, 2018, 4:04pm UTC](https://discuss.elastic.co/t/how-can-i-identify-back-pressure-in-logstash/157581/2 "2018-12-18T16:04:45Z")

</div>

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