# ES and KIBANA not keeping up with Suricata logs

**URL:** <https://discuss.elastic.co/t/es-and-kibana-not-keeping-up-with-suricata-logs/283636>\
**Category:** Kibana\
**Created:** [September 8, 2021, 9:29am UTC](https://discuss.elastic.co/t/es-and-kibana-not-keeping-up-with-suricata-logs/283636 "2021-09-08T09:29:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nunex\_17](https://avatars.discourse-cdn.com/v4/letter/n/f17d59/32.png) [@nunex\_17](https://discuss.elastic.co/u/nunex_17)\
**Post date:** [September 8, 2021, 9:29am UTC](https://discuss.elastic.co/t/es-and-kibana-not-keeping-up-with-suricata-logs/283636/1 "2021-09-08T09:29:31Z")

</div>

Hi.

I implemented a Suricata server with Filebeat to send logs to elasticsearch. The logs are then displayed in Kibana via the Filebeat Suricata module.

My problem is when I enable flow logging in the meericata log file. After a while, the logs displayed in Kibana are not in real time as if the tool were not following the flow of generated logs. Is there any way around this problem?

If I disable this kind of logging, everything works fine.

---

<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:** [October 6, 2021, 9:30am UTC](https://discuss.elastic.co/t/es-and-kibana-not-keeping-up-with-suricata-logs/283636/2 "2021-10-06T09:30:20Z")

</div>

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