<?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: How to configure props and transforms.conf to only index a few fields and ignore the other fields? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276433#M83400</link>
    <description>&lt;P&gt;Be aware that this approach has 2 drawbacks:&lt;/P&gt;

&lt;P&gt;1: Any index-time fields which are created by INDEXED_EXTRACTIONS (and maybe other ways, too), will still possess the values which proves that:&lt;BR /&gt;
2: Even though you will be "decluttering" your raw events, you will still be metered against your license for the pre-modified size.&lt;/P&gt;</description>
    <pubDate>Fri, 11 Dec 2015 03:32:47 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2015-12-11T03:32:47Z</dc:date>
    <item>
      <title>How to configure props and transforms.conf to only index a few fields and ignore the other fields?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276429#M83396</link>
      <description>&lt;P&gt;I tried all the possible things in Splunk, but couldn't index only some part of the file.&lt;/P&gt;

&lt;P&gt;For example:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2015/11/30 19:00:00 ad32ah req:connection srv:vm1pskndx3 method HTTPS txnid:986218312825 and from here 20 to 30 lines of event.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I need to index only &lt;CODE&gt;ad32ah&lt;/CODE&gt;, &lt;CODE&gt;vm1pskndx3&lt;/CODE&gt;, &lt;CODE&gt;HTTPS&lt;/CODE&gt; and &lt;CODE&gt;986218312825&lt;/CODE&gt;. I only need these 4 fields and ignore the other part of the event, and it should be repeated for all the events.&lt;/P&gt;

&lt;P&gt;I understand I should do something in &lt;CODE&gt;props.conf&lt;/CODE&gt; or &lt;CODE&gt;transforms.conf&lt;/CODE&gt;. &lt;/P&gt;

&lt;P&gt;Please advise!&lt;/P&gt;</description>
      <pubDate>Thu, 10 Dec 2015 14:52:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276429#M83396</guid>
      <dc:creator>allan_newton</dc:creator>
      <dc:date>2015-12-10T14:52:58Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure props and transforms.conf to only index a few fields and ignore the other fields?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276430#M83397</link>
      <description>&lt;P&gt;use your prop.conf as mentioned below(&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/admin/Propsconf&lt;/A&gt;)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SEDCMD-&amp;lt;class&amp;gt; = &amp;lt;sed script&amp;gt;
* Only used at index time.
* Commonly used to anonymize incoming data at index time, such as credit card or social
  security numbers. For more information, search the online documentation for "anonymize
  data."
* Used to specify a sed script which Splunk applies to the _raw field.
* A sed script is a space-separated list of sed commands. Currently the following subset of
  sed commands is supported:
        * replace (s) and character substitution (y).
* Syntax:
        * replace - s/regex/replacement/flags
                * regex is a perl regular expression (optionally containing capturing groups).
                * replacement is a string to replace the regex match. Use \n for back 
                  references, where "n" is a single digit.
                * flags can be either: g to replace all matches, or a number to replace a 
                  specified match.
        * substitute - y/string1/string2/
                * substitutes the string1[i] with string2[i]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 10 Dec 2015 15:05:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276430#M83397</guid>
      <dc:creator>renjith_nair</dc:creator>
      <dc:date>2015-12-10T15:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure props and transforms.conf to only index a few fields and ignore the other fields?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276431#M83398</link>
      <description>&lt;P&gt;But that is for anonymizing the incoming data.&lt;/P&gt;

&lt;P&gt;For example :&lt;/P&gt;

&lt;P&gt;1335-1235-1531-1353 is a card number and need to be indexed in a masked format xxxx-xxxx-xxxx-xx53.&lt;/P&gt;

&lt;P&gt;please correct me if I'm wrong.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Dec 2015 16:38:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276431#M83398</guid>
      <dc:creator>allan_newton</dc:creator>
      <dc:date>2015-12-10T16:38:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure props and transforms.conf to only index a few fields and ignore the other fields?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276432#M83399</link>
      <description>&lt;P&gt;Basically this is true, this doc talks about anonymizing data using a SED script... and what it does is match a pattern and replace it in the example.&lt;BR /&gt;
You should do the same, but replace it with nothing... You can try the effect using the Data onboarding wizard (Add Data)&lt;/P&gt;

&lt;P&gt;But it would be something like this in &lt;CODE&gt;props.conf&lt;/CODE&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SEDCMD - nullDataIDontWant = s/req:connection//g
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 10 Dec 2015 22:35:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276432#M83399</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-12-10T22:35:58Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure props and transforms.conf to only index a few fields and ignore the other fields?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276433#M83400</link>
      <description>&lt;P&gt;Be aware that this approach has 2 drawbacks:&lt;/P&gt;

&lt;P&gt;1: Any index-time fields which are created by INDEXED_EXTRACTIONS (and maybe other ways, too), will still possess the values which proves that:&lt;BR /&gt;
2: Even though you will be "decluttering" your raw events, you will still be metered against your license for the pre-modified size.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Dec 2015 03:32:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276433#M83400</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-12-11T03:32:47Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure props and transforms.conf to only index a few fields and ignore the other fields?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276434#M83401</link>
      <description>&lt;P&gt;How do I save my license ? Please help.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Dec 2015 11:26:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-configure-props-and-transforms-conf-to-only-index-a-few/m-p/276434#M83401</guid>
      <dc:creator>allan_newton</dc:creator>
      <dc:date>2015-12-14T11:26:06Z</dc:date>
    </item>
  </channel>
</rss>

