<?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: Regex error, exceeded configured match_limit in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Regex-error-exceeded-configured-match-limit/m-p/469891#M132224</link>
    <description>&lt;P&gt;any reason why you are performing a greedy rex&lt;BR /&gt;
consider changing to this&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; rex field=_raw  "NETWORK_STATE (?&amp;lt;Option1&amp;gt;\w+)(?&amp;lt;Option2&amp;gt;.*?)\- - -+\s+\"(?&amp;lt;NN1&amp;gt;.*?)\""


Basically , try replacing the MN fields .* with .*?
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;There are other fantastic answers here - &lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/35098/rex-matching-everything-until-a-tab.html"&gt;https://answers.splunk.com/answers/35098/rex-matching-everything-until-a-tab.html&lt;/A&gt;&lt;BR /&gt;
AND&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/727560/rex-has-exceeded-configured-match-limit.html"&gt;https://answers.splunk.com/answers/727560/rex-has-exceeded-configured-match-limit.html&lt;/A&gt;&lt;BR /&gt;
AND&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/581183/is-my-rex-right-rex-has-exceeded-configured-match.html"&gt;https://answers.splunk.com/answers/581183/is-my-rex-right-rex-has-exceeded-configured-match.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Just to cite a few&lt;/P&gt;</description>
    <pubDate>Sat, 31 Aug 2019 10:04:46 GMT</pubDate>
    <dc:creator>Sukisen1981</dc:creator>
    <dc:date>2019-08-31T10:04:46Z</dc:date>
    <item>
      <title>Regex error, exceeded configured match_limit</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Regex-error-exceeded-configured-match-limit/m-p/469890#M132223</link>
      <description>&lt;P&gt;Hi Splunkers,&lt;/P&gt;

&lt;P&gt;I'm running Splunk 7.0.1 and having some problems to parse variables using regex in a search.&lt;/P&gt;

&lt;P&gt;This is my data, in one line only:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Aug 30 19:40:41 10.181.132.181 1 2019-08-30T19:40:30.729124-04:00 bones NETWORK_STATE FACILITIES LINKS  - - - "All Power 1":1,"All Power 2":0,"Five Stars 1":1,"Five Stars 2":1,"Five Stars 3":1,"Five Stars 4":1,"Five Stars 5":1,"Five Stars 6":1,"Five Stars 7":1,"Five Stars Power":0,"Telefive Shark 1":1,"Telefive Shark 2":1,"Infinity 1":1,"Infinity 2":1,"Infinity 3":1,"OutSourcing":1,"Unitel":1,"Longside":1,"Tele Power":1,"Digilast 1":1,"Digilast 2":1&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;I'm trying to extract some fileds, like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Option1: FACILITIES
Option2: LINKS
NN1: "All Power 1"
Link_State1: 1
.
.
.
NN21: "Digilast 2"
Link_State21: 1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The regular expresion that I'm trying to use is:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;NETWORK_STATE (?&amp;lt;Option1&amp;gt;\w+) (?&amp;lt;Option2&amp;gt;\w+)  - - - 
(?&amp;lt;NN1&amp;gt;.*):(?&amp;lt;Link_State1&amp;gt;.)(?&amp;lt;NN2&amp;gt;.*):(?&amp;lt;Link_State2&amp;gt;.)(?&amp;lt;NN3&amp;gt;.*):(?&amp;lt;Link_State3&amp;gt;.)(?&amp;lt;NN4&amp;gt;.*):(?Link_State4&amp;gt;.)
(?&amp;lt;NN5&amp;gt;.*):(?&amp;lt;Link_State5&amp;gt;.)(?&amp;lt;NN6&amp;gt;.*):(?&amp;lt;Link_State6&amp;gt;.)(?&amp;lt;NN7&amp;gt;.*):(?&amp;lt;Link_State7&amp;gt;.)(?&amp;lt;NN8&amp;gt;.*):(?&amp;lt;Link_State8&amp;gt;.)
(?&amp;lt;NN9&amp;gt;.*):(?&amp;lt;Link_State9&amp;gt;.)(?&amp;lt;NN10&amp;gt;.*):(?&amp;lt;Link_State10&amp;gt;..)(?&amp;lt;NN11&amp;gt;.*):(?&amp;lt;Link_State11&amp;gt;..)(?&amp;lt;NN12&amp;gt;.*):(?&amp;lt;Link_State12&amp;gt;..)
(?&amp;lt;NN13&amp;gt;.*):(?&amp;lt;Link_State13&amp;gt;..)(?&amp;lt;NN14&amp;gt;.*):(?&amp;lt;Link_State14&amp;gt;..)(?&amp;lt;NN15&amp;gt;.*):(?&amp;lt;Link_State15&amp;gt;..)(?&amp;lt;NN16&amp;gt;.*):(?&amp;lt;Link_State16&amp;gt;..)
(?&amp;lt;NN17&amp;gt;.*):(?&amp;lt;Link_State17&amp;gt;..)(?&amp;lt;NN18&amp;gt;.*):(?&amp;lt;Link_State18&amp;gt;..)(?&amp;lt;NN19&amp;gt;.*):(?&amp;lt;Link_State19&amp;gt;..)(?&amp;lt;NN20&amp;gt;.*):(?&amp;lt;Link_State20&amp;gt;..)
(?&amp;lt;NN21&amp;gt;.*):(?&amp;lt;Link_State21&amp;gt;..)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But I've got the following error:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Error in 'rex' command: regex="NETWORK_STATE (?&amp;lt;Option1&amp;gt;\w+) (?&amp;lt;Option2&amp;gt;\w+) - - - (?&amp;lt;NN1&amp;gt;.*),(?&amp;lt;NN10&amp;gt;.*):(?&amp;lt;Link_State10&amp;gt;.), 
(?&amp;lt;NN11&amp;gt;.*):(?&amp;lt;Link_State11&amp;gt;.),(?&amp;lt;NN12&amp;gt;.*):(?&amp;lt;Link_State12&amp;gt;.),(?&amp;lt;NN13&amp;gt;.*):(?&amp;lt;Link_State13&amp;gt;.),(?&amp;lt;NN14&amp;gt;.*):(?&amp;lt;Link_State14&amp;gt;.),(? 
&amp;lt;NN15&amp;gt;.*):(?&amp;lt;Link_State15&amp;gt;.),(?&amp;lt;NN16&amp;gt;.*):(?&amp;lt;Link_State16&amp;gt;.),(?&amp;lt;NN17&amp;gt;.*):(?&amp;lt;Link_State17&amp;gt;.),(?&amp;lt;NN18&amp;gt;.*):(?&amp;lt;Link_State18&amp;gt;.),(? 
&amp;lt;NN19&amp;gt;.*):(?&amp;lt;Link_State19&amp;gt;.),(?&amp;lt;NN20&amp;gt;.*):(?&amp;lt;Link_State20&amp;gt;.),(?&amp;lt;NN21&amp;gt;.*):(?&amp;lt;Link_State21&amp;gt;.)" has exceeded configured match_limit, 
consider raising the value in limits.conf
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Looking for the error, I've learnt that there is better ways to achieve my goal. Please, could yo enlight me?&lt;/P&gt;

&lt;P&gt;Regards&lt;/P&gt;

&lt;P&gt;Pedro&lt;/P&gt;</description>
      <pubDate>Sat, 31 Aug 2019 01:19:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Regex-error-exceeded-configured-match-limit/m-p/469890#M132223</guid>
      <dc:creator>prsepulv</dc:creator>
      <dc:date>2019-08-31T01:19:45Z</dc:date>
    </item>
    <item>
      <title>Re: Regex error, exceeded configured match_limit</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Regex-error-exceeded-configured-match-limit/m-p/469891#M132224</link>
      <description>&lt;P&gt;any reason why you are performing a greedy rex&lt;BR /&gt;
consider changing to this&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; rex field=_raw  "NETWORK_STATE (?&amp;lt;Option1&amp;gt;\w+)(?&amp;lt;Option2&amp;gt;.*?)\- - -+\s+\"(?&amp;lt;NN1&amp;gt;.*?)\""


Basically , try replacing the MN fields .* with .*?
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;There are other fantastic answers here - &lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/35098/rex-matching-everything-until-a-tab.html"&gt;https://answers.splunk.com/answers/35098/rex-matching-everything-until-a-tab.html&lt;/A&gt;&lt;BR /&gt;
AND&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/727560/rex-has-exceeded-configured-match-limit.html"&gt;https://answers.splunk.com/answers/727560/rex-has-exceeded-configured-match-limit.html&lt;/A&gt;&lt;BR /&gt;
AND&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/581183/is-my-rex-right-rex-has-exceeded-configured-match.html"&gt;https://answers.splunk.com/answers/581183/is-my-rex-right-rex-has-exceeded-configured-match.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Just to cite a few&lt;/P&gt;</description>
      <pubDate>Sat, 31 Aug 2019 10:04:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Regex-error-exceeded-configured-match-limit/m-p/469891#M132224</guid>
      <dc:creator>Sukisen1981</dc:creator>
      <dc:date>2019-08-31T10:04:46Z</dc:date>
    </item>
    <item>
      <title>Re: Regex error, exceeded configured match_limit</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Regex-error-exceeded-configured-match-limit/m-p/469892#M132225</link>
      <description>&lt;P&gt;It works like a charm.&lt;/P&gt;

&lt;P&gt;Thank you very much...!!!&lt;/P&gt;</description>
      <pubDate>Sat, 31 Aug 2019 17:18:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Regex-error-exceeded-configured-match-limit/m-p/469892#M132225</guid>
      <dc:creator>prsepulv</dc:creator>
      <dc:date>2019-08-31T17:18:30Z</dc:date>
    </item>
  </channel>
</rss>

