<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Rex has exceeded configured match_limit, consider raising the value in limits.conf. in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Rex-has-exceeded-configured-match-limit-consider-raising-the/m-p/684568#M233672</link>
    <description>&lt;P&gt;Yes you could exclude successful responses by adding a filter. Assuming that all errors have an errorCode and all non-errors do not, then you could do it like this:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index = xxx sourcetype=xxx "Publish message on SQS" bulkDelete
| rex field=_raw "message=(?&amp;lt;message&amp;gt;{.*}$)"
| spath input=message
| search "errors{}.errorCode" = *
| spath input=errors{}.errorDetails
| table eventSource statusCode statusText&lt;/LI-CODE&gt;</description>
    <pubDate>Wed, 17 Apr 2024 21:17:10 GMT</pubDate>
    <dc:creator>marnall</dc:creator>
    <dc:date>2024-04-17T21:17:10Z</dc:date>
    <item>
      <title>Rex has exceeded configured match_limit, consider raising the value in limits.conf.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Rex-has-exceeded-configured-match-limit-consider-raising-the/m-p/684416#M233646</link>
      <description>&lt;P&gt;In our log, I'd like to extract&amp;nbsp;&lt;SPAN class=""&gt;statusText and categorize it in table to see how many error response statusCode and statusText.&lt;BR /&gt;EX:&lt;/SPAN&gt;&lt;/P&gt;&lt;TABLE border="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="33.333333333333336%"&gt;&lt;SPAN class=""&gt;eventSource&lt;/SPAN&gt;&lt;/TD&gt;&lt;TD width="33.333333333333336%"&gt;&lt;SPAN class=""&gt;statusCode&lt;/SPAN&gt;&lt;/TD&gt;&lt;TD width="33.333333333333336%"&gt;&lt;SPAN class=""&gt;statusText&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="33.333333333333336%"&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;bulkDelete&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/TD&gt;&lt;TD width="33.333333333333336%"&gt;1020&lt;/TD&gt;&lt;TD width="33.333333333333336%"&gt;&lt;SPAN class=""&gt;3031:&lt;/SPAN&gt; &lt;SPAN class=""&gt;No&lt;/SPAN&gt; &lt;SPAN class=""&gt;Card&lt;/SPAN&gt; &lt;SPAN class=""&gt;found&lt;/SPAN&gt; &lt;SPAN class=""&gt;with&lt;/SPAN&gt; &lt;SPAN class=""&gt;the&lt;/SPAN&gt; &lt;SPAN class=""&gt;identifier&lt;/SPAN&gt; &lt;SPAN class=""&gt;for&lt;/SPAN&gt; &lt;SPAN class=""&gt;the&lt;/SPAN&gt; &lt;SPAN class=""&gt;request&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But my query is getting "&lt;SPAN&gt;has exceeded configured match_limit, consider raising the value in limits.conf.&lt;/SPAN&gt;" after using fields extraction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index = xxx sourcetype=xxx "Publish message on SQS" | search bulkDelete | rex field=_raw "(?ms)^(?:[^:\\n]*:){7}\"(?P&amp;lt;error_bulkDelete&amp;gt;[^\"]+)(?:[^:\\n]*:){2}\"(?P&amp;lt;error_errorCode&amp;gt;[^\"]+)[^:\\n]*:\"(?P&amp;lt;error_desc&amp;gt;[^\"]+)(?:[^:\\n]*:){6}\\\\\"(?P&amp;lt;error_statusText&amp;gt;[^\\\\]+)" offset_field=_extracted_fields_bounds&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Target log:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Publish message on SQS, queueName=xxx, retryCount=0, message={"traceId":"xxx1112233","clientContext":"xxxxxclientContext","cardTokenReferenceId":"xxxcardTokenReferenceId","eventSource":"bulkDelete","errors":[{"errorCode":"52099","errorDescription":"Feign Client Exception.","retryCategory":"RETRYABLE","errorDetails":"{\"clientContext\":\"xxxxxclientContext\",\"ewSID\":\"xxxxSID\",\"statusCode\":\"1020\",\"statusText\":\"3031: No Card found with the identifier for the request\",\"timestampISO8601\":\"2024-04-05T00:00:26Z\"}"}]}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I checked similar posts, they suggested to use non-greedy?&lt;/P&gt;&lt;P&gt;So I tried:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index = "xxx" sourcetype=xxx "Publish message on SQS*" bulkDelete | rex field=_raw "\"statusText\":\s*\"(?P&amp;lt;statusText&amp;gt;[^\"]+)\"" | where NOT LIKE( statusText, "%Success%")&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I add "| table", I will get blank content on&amp;nbsp;statusText&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2024 20:15:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Rex-has-exceeded-configured-match-limit-consider-raising-the/m-p/684416#M233646</guid>
      <dc:creator>ssh</dc:creator>
      <dc:date>2024-04-16T20:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: Rex has exceeded configured match_limit, consider raising the value in limits.conf.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Rex-has-exceeded-configured-match-limit-consider-raising-the/m-p/684418#M233648</link>
      <description>&lt;P&gt;You could try extracting the json object after message=, then spathing it until you get the fields you would like. E.g.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index = xxx sourcetype=xxx "Publish message on SQS" bulkDelete
| rex field=_raw "message=(?&amp;lt;message&amp;gt;{.*}$)"
| spath input=message
| spath input=errors{}.errorDetails
| table eventSource statusCode statusText&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2024 19:59:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Rex-has-exceeded-configured-match-limit-consider-raising-the/m-p/684418#M233648</guid>
      <dc:creator>marnall</dc:creator>
      <dc:date>2024-04-16T19:59:38Z</dc:date>
    </item>
    <item>
      <title>Re: Rex has exceeded configured match_limit, consider raising the value in limits.conf.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Rex-has-exceeded-configured-match-limit-consider-raising-the/m-p/684424#M233649</link>
      <description>&lt;P&gt;Thanks, it looks like contain successful response, can we exclude it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Publish message on SQS, queueName=xxx, retryCount=0, message={"traceId":"xxxtraceId","clientContext":"xxxclientContext","cardTokenReferenceId":"xxxCardTokenReferenceId","eventSource":"bulkDelete","walletWebResponse":{"clientContext":"xxxclientContext","ewSID":"xxxSID,"timestampISO8601":"2024-04-05T00:00:14Z","statusCode":"0","statusText":"Success"}}&lt;/LI-CODE&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-04-16 at 2.40.42 PM.png" style="width: 999px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/30419i2835FC3EB3241327/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot 2024-04-16 at 2.40.42 PM.png" alt="Screenshot 2024-04-16 at 2.40.42 PM.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2024 21:42:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Rex-has-exceeded-configured-match-limit-consider-raising-the/m-p/684424#M233649</guid>
      <dc:creator>ssh</dc:creator>
      <dc:date>2024-04-16T21:42:58Z</dc:date>
    </item>
    <item>
      <title>Re: Rex has exceeded configured match_limit, consider raising the value in limits.conf.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Rex-has-exceeded-configured-match-limit-consider-raising-the/m-p/684568#M233672</link>
      <description>&lt;P&gt;Yes you could exclude successful responses by adding a filter. Assuming that all errors have an errorCode and all non-errors do not, then you could do it like this:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index = xxx sourcetype=xxx "Publish message on SQS" bulkDelete
| rex field=_raw "message=(?&amp;lt;message&amp;gt;{.*}$)"
| spath input=message
| search "errors{}.errorCode" = *
| spath input=errors{}.errorDetails
| table eventSource statusCode statusText&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 17 Apr 2024 21:17:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Rex-has-exceeded-configured-match-limit-consider-raising-the/m-p/684568#M233672</guid>
      <dc:creator>marnall</dc:creator>
      <dc:date>2024-04-17T21:17:10Z</dc:date>
    </item>
  </channel>
</rss>

