<?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 Field extractor warning. in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Field-extractor-warning/m-p/97686#M25195</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Lately when I run searches I tend to get a warning on the screen along the lines of:&lt;/P&gt;

&lt;PRE&gt;
Field extractor name=access-extractions is unusually slow (max single event time=1140ms, probes=375 warning max=1000ms)
&lt;/PRE&gt;

&lt;P&gt;What causes this, and, what should I be looking at to tweak to make Splunk happy again?&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Mon, 09 May 2011 06:05:11 GMT</pubDate>
    <dc:creator>howyagoin</dc:creator>
    <dc:date>2011-05-09T06:05:11Z</dc:date>
    <item>
      <title>Field extractor warning.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extractor-warning/m-p/97686#M25195</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Lately when I run searches I tend to get a warning on the screen along the lines of:&lt;/P&gt;

&lt;PRE&gt;
Field extractor name=access-extractions is unusually slow (max single event time=1140ms, probes=375 warning max=1000ms)
&lt;/PRE&gt;

&lt;P&gt;What causes this, and, what should I be looking at to tweak to make Splunk happy again?&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2011 06:05:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extractor-warning/m-p/97686#M25195</guid>
      <dc:creator>howyagoin</dc:creator>
      <dc:date>2011-05-09T06:05:11Z</dc:date>
    </item>
    <item>
      <title>Re: Field extractor warning.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extractor-warning/m-p/97687#M25196</link>
      <description>&lt;P&gt;Howyagoin,&lt;/P&gt;

&lt;P&gt;This is a warning message introduced in 4.2.1.  It will warn when extractions exceed 1000ms.  I have browsed limits.conf without finding a setting to increase this threshold; however I would recommend addressing the underlying extraction.&lt;/P&gt;

&lt;P&gt;In this case the "access-extractions" transform Regex may need to be adjusted to provide faster matching.  This typically involves anchors which will invalidate the match quicker.&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2011 20:12:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extractor-warning/m-p/97687#M25196</guid>
      <dc:creator>hazekamp</dc:creator>
      <dc:date>2011-05-10T20:12:38Z</dc:date>
    </item>
    <item>
      <title>Re: Field extractor warning.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extractor-warning/m-p/97688#M25197</link>
      <description>&lt;P&gt;Thanks for this - I spent some time staring at it and came to the same conclusion last night -- I fear what triggered it was a somewhat imprecise search I was conducting which was indeed going through httpd access files which were indexed.  I'll have to work on adding sourcetypes to searches a bit more.  Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2011 20:35:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extractor-warning/m-p/97688#M25197</guid>
      <dc:creator>howyagoin</dc:creator>
      <dc:date>2011-05-10T20:35:58Z</dc:date>
    </item>
  </channel>
</rss>

