topic Re: Why are events are not displayed in the search results because _raw fields exceed the limit of 16777216 characters? in Splunk Search

Why are events are not displayed in the search results because _raw fields exceed the limit of 16777216 characters?

ssuluguri — Wed, 05 Apr 2023 19:23:13 GMT

Hi Team

I am getting below warning notification from indexers , can someone help how to clear this .

"Search peer XXXX has the following message: Events are not displayed in the search results because _raw fields exceed the limit of 16777216 characters. Ensure that _raw fields are below the given character limit or switch to the CSV serialization format by setting 'results_serial_format=csv' in limits.conf. Switching to the CSV serialization format will reduce search performance"

Re: Why are events are not displayed in the search results because _raw fields exceed the limit of 16777216 characters?

woodcock — Wed, 05 Apr 2023 21:53:19 GMT

The problem is exactly what it says it is. The situation is EITHER:
A: You are NOTlinbreaking the file correctly and each current event is actually MANY events
B: You ARE linebreaking the file correctly and each current event really is HUUUUGE.

In the case of the former, just fix it. In the case of the latter, you will have to reformat the original logs to ensure that each event is smaller the inescapable limit. We usually use cribl for this but it is more than we can talk about in here because there is bunch of depends. I am easy to find so reach out to me if you are in the latter boat.

Re: Why are events are not displayed in the search results because _raw fields exceed the limit of 16777216 characters?

JNgoho — Wed, 07 Jun 2023 02:55:36 GMT

is there a way to identify what logs are those?

Re: Why are events are not displayed in the search results because _raw fields exceed the limit of 16777216 characters?

isoutamo — Wed, 07 Jun 2023 04:38:29 GMT

probably you could found those by searching for _internal? I haven’t have this kind of situation, sou I couldn’t give you a SPL for that. Another option is look your current search which has given that warning. Then just create search like

<your base from previous search> |eval len =length(_raw) | fields host source sourcetype len | where len > <max length from error message>

r. Ismo