# Filebeat error

**URL:** <https://discuss.elastic.co/t/filebeat-error/257666>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 4, 2020, 2:31pm UTC](https://discuss.elastic.co/t/filebeat-error/257666 "2020-12-04T14:31:51Z")\
**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:** [December 4, 2020, 2:31pm UTC](https://discuss.elastic.co/t/filebeat-error/257666/1 "2020-12-04T14:31:51Z")

</div>

Hi. I am using the ELK with filebeat sending logs to elastic via suricata module. I have all configured but after some time the information on "discover" and "dashboard" just disappears. On the elastic and filebeat logs no error seems to appear. But if i do "systemctl status filebeat", the following error shows up.

' (status=400): {"type":"mapper\_parsing\_exception","reason":"failed to parse","caused\_by":{"type":"illegal\_argument\_exception","reason":"Cannot write to a field alias [suricata.eve.flow.start]."}}

---

<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:** [January 1, 2021, 4:32pm UTC](https://discuss.elastic.co/t/filebeat-error/257666/2 "2021-01-01T16:32:04Z")

</div>

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