# Logstash/Filebeat lag issue - Logs delayed by hours

**URL:** https://discuss.elastic.co/t/logstash-filebeat-lag-issue-logs-delayed-by-hours/385101
**Category:** Beats
**Tags:** filebeat
**Created:** [February 18, 2026, 5:00pm UTC](https://discuss.elastic.co/t/logstash-filebeat-lag-issue-logs-delayed-by-hours/385101 "2026-02-18T17:00:34Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)
#### Post date: [February 19, 2026, 1:34am UTC](https://discuss.elastic.co/t/logstash-filebeat-lag-issue-logs-delayed-by-hours/385101/12 "2026-02-19T01:34:21Z")

</div>

There was a similar problem, check [this topic](https://discuss.elastic.co/t/filebeat-clients-unable-to-publish-events-to-logstash/378592).  
Most likely you have network issues, not just the lag like FB processing speed.

As Leandro Jedi said, remove `stdin` and `stdout`, especially debug because it consumes a lot of resources.

Since you are using different version, make sure to us the same version or at least upgrade FB. This is not mandatory, of course.

> Since I have a high volume of logs and a single Logstash instance with many cores, I configured multiple listeners to avoid a single TCP thread bottleneck at the input stage

Why don't you use LS pipelines? Separate .conf files. Maybe even you can use much faster the dissect parser filter in some cases.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-filebeat-lag-issue-logs-delayed-by-hours/385101)._