# Messages that contain more than 32766 bytes in a field **URL:** \ **Category:** Logstash\ **Created:** [August 3, 2020, 11:36am UTC](https://discuss.elastic.co/t/messages-that-contain-more-than-32766-bytes-in-a-field/243545 "2020-08-03T11:36:20Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![sarabande](https://avatars.discourse-cdn.com/v4/letter/s/7cd45c/32.png) [@sarabande](https://discuss.elastic.co/u/sarabande)\ **Post date:** [August 3, 2020, 11:36am UTC](https://discuss.elastic.co/t/messages-that-contain-more-than-32766-bytes-in-a-field/243545/1 "2020-08-03T11:36:20Z")
Hi, I have a general question. What happens with messages that contain fields longer than 32766 bytes? They will cause the error saying something like "Could not index event to Elasticsearch" and "caused\_by"=\>{"type"=\>"max\_bytes\_length\_exceeded\_exception", "reason"=\>"max\_bytes\_length\_exceeded\_exception: bytes can be at most 32766 in length; got 276223"}. But will it be tagged with any of \_\*failure tags (like \_grokparsefailure, \_jsonparsefailure, etc.)? I know that if grok cannot prase the message according to it's filter the message will be tagged with \_grokparsefailure, failure in parsing json will probably cause the message to be tagged with \_jsonparsefailure and so on. Is there any such a tag for messages that contain fields longer than the limit (32766 bytes)? I could not find anywhere is the documentation the list of existing \_\*failure tags. Is there any? Thanks. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 31, 2020, 11:36am UTC](https://discuss.elastic.co/t/messages-that-contain-more-than-32766-bytes-in-a-field/243545/2 "2020-08-31T11:36:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.