<?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: Ignore Dynamic KV Creation in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234664#M69728</link>
    <description>&lt;P&gt;This probably will not work unless you use &lt;CODE&gt;SEDCMD&lt;/CODE&gt; instead of &lt;CODE&gt;sedcmd&lt;/CODE&gt;.&lt;/P&gt;</description>
    <pubDate>Wed, 02 Dec 2015 20:59:51 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2015-12-02T20:59:51Z</dc:date>
    <item>
      <title>Ignore Dynamic KV Creation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234659#M69723</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm trying to get to grips with CIM and am getting there slowly, however, I hit a snag that I can't seem to get around and it makes one of my field extraction result 'ugly'!!&lt;/P&gt;

&lt;P&gt;I've got a load of events from different sources in my &lt;CODE&gt;eventtype="Authenticate"&lt;/CODE&gt; type. In nearly every case, I've had to create a dynamic field extraction called &lt;CODE&gt;action&lt;/CODE&gt; ( as per the CIM model name ) for the &lt;CODE&gt;Success/Fail&lt;/CODE&gt; status. So far so good.&lt;/P&gt;

&lt;P&gt;I've started ingesting another &lt;CODE&gt;Authentication&lt;/CODE&gt; type log which, unfortunately contains the KV field - &lt;CODE&gt;action=some_unique_string&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Is there any way that I can get Splunk to either ignore this KV or change the key to something other than &lt;CODE&gt;action&lt;/CODE&gt; so that I can use my own &lt;CODE&gt;action&lt;/CODE&gt; field extraction?&lt;/P&gt;

&lt;P&gt;Thanks, Mark.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2015 13:34:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234659#M69723</guid>
      <dc:creator>markwymer</dc:creator>
      <dc:date>2015-11-13T13:34:36Z</dc:date>
    </item>
    <item>
      <title>Re: Ignore Dynamic KV Creation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234660#M69724</link>
      <description>&lt;P&gt;You could use a more narrow field extraction for your "own" action field.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;(?&amp;lt;action&amp;gt;(?&amp;lt;=action=)(Success|Fail))
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This would only extract a field called action if it matched "action=" followed by "Success" or "Fail".  It will not extract the action field otherwise.&lt;/P&gt;

&lt;P&gt;You can use this in search with rex command or otherwise by using the "report" options in props.conf &amp;amp; transforms.conf&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2015 13:43:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234660#M69724</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2015-11-13T13:43:47Z</dc:date>
    </item>
    <item>
      <title>Re: Ignore Dynamic KV Creation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234661#M69725</link>
      <description>&lt;P&gt;You need to put this in &lt;CODE&gt;props.conf&lt;/CODE&gt; to turn off the automatic field extraction but it will do so for all fields in the entire sourcetype:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;KV_MODE = none
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 13 Nov 2015 15:32:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234661#M69725</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-11-13T15:32:21Z</dc:date>
    </item>
    <item>
      <title>Re: Ignore Dynamic KV Creation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234662#M69726</link>
      <description>&lt;P&gt;KV_MODE is too useful to turn off for this case.&lt;BR /&gt;
Because lookups are executed after field aliases, you can alias your existing action field to some other name (like vendor_action) and then overwrite it with your lookup. This way you get both. &lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 07:54:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234662#M69726</guid>
      <dc:creator>mreynov_splunk</dc:creator>
      <dc:date>2020-09-29T07:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: Ignore Dynamic KV Creation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234663#M69727</link>
      <description>&lt;P&gt;I see the issue more clearly now.&lt;/P&gt;

&lt;P&gt;For the new "Authentication" source, rename the field upon ingestion.&lt;/P&gt;

&lt;P&gt;in props.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[sourcetype]
sedcmd-renamer = s/action=/authaction=/g
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 02 Dec 2015 12:36:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234663#M69727</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2015-12-02T12:36:32Z</dc:date>
    </item>
    <item>
      <title>Re: Ignore Dynamic KV Creation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234664#M69728</link>
      <description>&lt;P&gt;This probably will not work unless you use &lt;CODE&gt;SEDCMD&lt;/CODE&gt; instead of &lt;CODE&gt;sedcmd&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Dec 2015 20:59:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Ignore-Dynamic-KV-Creation/m-p/234664#M69728</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-12-02T20:59:51Z</dc:date>
    </item>
  </channel>
</rss>

