<?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: Is there any way to *selectively* avoid automatic field extraction? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43389#M10200</link>
    <description>&lt;P&gt;The trouble is that there's a huge number of fields for which I need the normal equals sign autokv extraction to work.  I tried specifying a manual regex for equals but there's a bunch of subtlety that autokv just does really well when you look at it under a microscope and I couldnt get the manual regex to the desired standard.&lt;/P&gt;</description>
    <pubDate>Sun, 13 Feb 2011 04:08:17 GMT</pubDate>
    <dc:creator>sideview</dc:creator>
    <dc:date>2011-02-13T04:08:17Z</dc:date>
    <item>
      <title>Is there any way to *selectively* avoid automatic field extraction?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43385#M10196</link>
      <description>&lt;P&gt;I have multiline events where there's a fair bit of auto-kv extraction that is good, but then there's a lot of noise as well. &lt;/P&gt;

&lt;P&gt;I can create regexes to match the really noisy bits and this works well.  I nearly get perfect coverage on the high-value fields that I actually need.  &lt;/P&gt;

&lt;P&gt;The problem is that even when I have a regex matching, sometimes the same field appears in a foo=bar pair further down into the event, and the autoKV match is clobbering my more explicit regex match.  Can someone point me in the right direction? (Obviously the answer is to make the logging less deranged, but it's not an option atm unfortunateley)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;-------------------------------------
Fields: Field=GoodValue;foo=bar;jackiechan=theman
AnotherGoodField = AnotherGoodValue
User = bob
.....
Field : BadNoisyValueThatClobbersMyGoodValue
-------------------------------------
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;One idea is - can I tell the autokv stuff not to pay attention to colons?  All the colon stuff is hideously noisy in this sourcetype.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Feb 2011 05:42:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43385#M10196</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2011-02-12T05:42:52Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to *selectively* avoid automatic field extraction?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43386#M10197</link>
      <description>&lt;P&gt;You could disable KV discovery for a particular source, host, or sourcetype in &lt;STRONG&gt;props.conf&lt;/STRONG&gt;.  Maybe this would help:&lt;/P&gt;

&lt;P&gt;PROPS.CONF:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[mysourcetype]
KV_MODE = none 
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 12 Feb 2011 06:35:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43386#M10197</guid>
      <dc:creator>Ron_Naken</dc:creator>
      <dc:date>2011-02-12T06:35:03Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to *selectively* avoid automatic field extraction?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43387#M10198</link>
      <description>&lt;P&gt;I don't believe it looks for colons, by default.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Feb 2011 06:37:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43387#M10198</guid>
      <dc:creator>Ron_Naken</dc:creator>
      <dc:date>2011-02-12T06:37:20Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to *selectively* avoid automatic field extraction?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43388#M10199</link>
      <description>&lt;P&gt;From what I can tell it's definitely matching colons all over the place.&lt;/P&gt;</description>
      <pubDate>Sun, 13 Feb 2011 04:04:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43388#M10199</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2011-02-13T04:04:41Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to *selectively* avoid automatic field extraction?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43389#M10200</link>
      <description>&lt;P&gt;The trouble is that there's a huge number of fields for which I need the normal equals sign autokv extraction to work.  I tried specifying a manual regex for equals but there's a bunch of subtlety that autokv just does really well when you look at it under a microscope and I couldnt get the manual regex to the desired standard.&lt;/P&gt;</description>
      <pubDate>Sun, 13 Feb 2011 04:08:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43389#M10200</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2011-02-13T04:08:17Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to *selectively* avoid automatic field extraction?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43390#M10201</link>
      <description>&lt;P&gt;It does the colon matching in WinEventLog:: (and maybe WMI::) sourcetypes.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2011 09:54:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43390#M10201</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-02-15T09:54:55Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to *selectively* avoid automatic field extraction?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43391#M10202</link>
      <description>&lt;P&gt;The colon matching isn't handled by the KV_MODE switch, but by a different search-time extract.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2011 09:55:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-any-way-to-selectively-avoid-automatic-field-extraction/m-p/43391#M10202</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-02-15T09:55:25Z</dc:date>
    </item>
  </channel>
</rss>

