# Filebeat syslog problem

**URL:** <https://discuss.elastic.co/t/filebeat-syslog-problem/301328>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 1, 2022, 1:43pm UTC](https://discuss.elastic.co/t/filebeat-syslog-problem/301328 "2022-04-01T13:43:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![adis3421](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@adis3421](https://discuss.elastic.co/u/adis3421)\
**Post date:** [April 1, 2022, 1:43pm UTC](https://discuss.elastic.co/t/filebeat-syslog-problem/301328/1 "2022-04-01T13:43:12Z")

</div>

Hi,

I using filebeat via logstash and normaly connect to elasticsearch. In normal connect is ok but via logstash I have a problem:

## illegal\_argument\_exception at `shard` 0 `index` filebeat-8.1.2-2022.04.01 `node` x1NX6Z2sRz2pH9YrYLI70w

Type

illegal\_argument\_exception

Reason

Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [host.hostname] in order to load field data by uninverting the inverted index. Note that this can use significant memory.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/9/d9b226b87b52f4351a3ba7e1c22a485d3dfa8633.png)

---

<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:** [April 29, 2022, 3:43pm UTC](https://discuss.elastic.co/t/filebeat-syslog-problem/301328/2 "2022-04-29T15:43:51Z")

</div>

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