<?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: Creating field value pair in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Creating-field-value-pair/m-p/132331#M1350</link>
    <description>&lt;P&gt;This worked just make sure to use quotes&lt;/P&gt;</description>
    <pubDate>Thu, 06 Feb 2014 14:51:01 GMT</pubDate>
    <dc:creator>splunkingsplun1</dc:creator>
    <dc:date>2014-02-06T14:51:01Z</dc:date>
    <item>
      <title>Creating field value pair</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Creating-field-value-pair/m-p/132328#M1347</link>
      <description>&lt;P&gt;According to the documentation &lt;A href="http://docs.splunk.com/Documentation/CIM/3.0.1/User/IntrusionDetection/" title="Title"&gt;here&lt;/A&gt; I need to have ids_type in my events as follows ids_type="network" or ids_type="application" or ids_type="host". How can I add a field value pair to my events automatically? Would I have to create this in transforms.conf?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[netdefender]
REGEX =  Netdefender
FORMAT = ids_type=network
WRITE_META = true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This is a portion of a sample event:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Jan 30 10:32:43 192.168.1.1 Netdefender: 30-01-2014 02:54:05 WARNING
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I am not sure how this works its been a long day. Help please!&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2014 21:05:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Creating-field-value-pair/m-p/132328#M1347</guid>
      <dc:creator>splunkingsplun1</dc:creator>
      <dc:date>2014-01-30T21:05:51Z</dc:date>
    </item>
    <item>
      <title>Re: Creating field value pair</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Creating-field-value-pair/m-p/132329#M1348</link>
      <description>&lt;P&gt;first of all you would need to specify something to extract in the regex, could we see some sample code in order to help you?&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2014 02:59:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Creating-field-value-pair/m-p/132329#M1348</guid>
      <dc:creator>asimagu</dc:creator>
      <dc:date>2014-02-03T02:59:49Z</dc:date>
    </item>
    <item>
      <title>Re: Creating field value pair</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Creating-field-value-pair/m-p/132330#M1349</link>
      <description>&lt;P&gt;If you want to add an additional field for each sourcetype you can use calculated fields.&lt;/P&gt;

&lt;P&gt;e.g. &lt;BR /&gt;
props.conf (assuming 'netdefender' is your sourcetype name)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[netdefender]
pulldown_type = 1
EVAL-ids_type = "network"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This will add a field ids_type="network" for all the logs in sourcetype "netdefender"&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2014 14:36:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Creating-field-value-pair/m-p/132330#M1349</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2014-02-03T14:36:02Z</dc:date>
    </item>
    <item>
      <title>Re: Creating field value pair</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Creating-field-value-pair/m-p/132331#M1350</link>
      <description>&lt;P&gt;This worked just make sure to use quotes&lt;/P&gt;</description>
      <pubDate>Thu, 06 Feb 2014 14:51:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Creating-field-value-pair/m-p/132331#M1350</guid>
      <dc:creator>splunkingsplun1</dc:creator>
      <dc:date>2014-02-06T14:51:01Z</dc:date>
    </item>
  </channel>
</rss>

