# Suricata logs over Filebeat **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [March 26, 2021, 7:50pm UTC](https://discuss.elastic.co/t/suricata-logs-over-filebeat/268538 "2021-03-26T19:50:38Z")\ **Posts on this page:** 3\ **Page:** 1
**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:** [March 26, 2021, 7:50pm UTC](https://discuss.elastic.co/t/suricata-logs-over-filebeat/268538/1 "2021-03-26T19:50:38Z")
Hi. I am sending Suricata logs with filebeat to a ELK server. I have the eve.json configured to rotate every day at midnight. Logs are being sent to elastic and I can see them in the dashboards and discover tabs. But in fact, it not shows the current logs. I have to select the 24h period and then the logs are shown with the correct timestamp (but from hours ago). For example, now are being shown logs from today at midnight. At the time of this post, it´s currently 7pm. So there's like a 20h hour difference. How can I solve this issue? ---
**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\ **Post date:** [March 28, 2021, 4:56pm UTC](https://discuss.elastic.co/t/suricata-logs-over-filebeat/268538/2 "2021-03-28T16:56:27Z")
I would check the timestamps of the raw log files, the time & time zone of both the system running suricata and your workstation. The most common cause of time issues that I've had is timezones not being correct. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 25, 2021, 6:56pm UTC](https://discuss.elastic.co/t/suricata-logs-over-filebeat/268538/3 "2021-04-25T18:56:39Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.