<?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 customize what TERM() can hit on in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-customize-what-TERM-can-hit-on/m-p/225857#M98948</link>
    <description>&lt;P&gt;Altering what segments can be searched with TERM involves changing the segmenters.conf: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.6.2/Admin/Segmentersconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.6.2/Admin/Segmentersconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Be aware that changes in the characters for major and minor segmenters in the default stanza will have a big effect on ALL data indexed and the disk space required for indexed data.  To affect a particular sourcetype, reference it in the stanza name.&lt;/P&gt;

&lt;P&gt;.. Or to your other question and more simply/safely, you could just create a transforms that indexes a field of interest at index time which could key on an indexed field and would be called from props on a sourcetype basis.&lt;/P&gt;</description>
    <pubDate>Fri, 28 Jul 2017 22:29:19 GMT</pubDate>
    <dc:creator>landen99</dc:creator>
    <dc:date>2017-07-28T22:29:19Z</dc:date>
    <item>
      <title>How to customize what TERM() can hit on</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-customize-what-TERM-can-hit-on/m-p/225856#M98947</link>
      <description>&lt;P&gt;I want to be able to use TERM() on complicated values such as HTTP URLs and user agent strings. Usually, this does not work due to spaces and other breaking characters.&lt;/P&gt;

&lt;P&gt;Is there a way to customize the terms at all? Hopefully on a sourctype and field basis?&lt;/P&gt;

&lt;P&gt;If not possible, would other solutions like summary indexing help&amp;gt;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2016 18:27:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-customize-what-TERM-can-hit-on/m-p/225856#M98947</guid>
      <dc:creator>thisissplunk</dc:creator>
      <dc:date>2016-04-28T18:27:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to customize what TERM() can hit on</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-customize-what-TERM-can-hit-on/m-p/225857#M98948</link>
      <description>&lt;P&gt;Altering what segments can be searched with TERM involves changing the segmenters.conf: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.6.2/Admin/Segmentersconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.6.2/Admin/Segmentersconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Be aware that changes in the characters for major and minor segmenters in the default stanza will have a big effect on ALL data indexed and the disk space required for indexed data.  To affect a particular sourcetype, reference it in the stanza name.&lt;/P&gt;

&lt;P&gt;.. Or to your other question and more simply/safely, you could just create a transforms that indexes a field of interest at index time which could key on an indexed field and would be called from props on a sourcetype basis.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jul 2017 22:29:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-customize-what-TERM-can-hit-on/m-p/225857#M98948</guid>
      <dc:creator>landen99</dc:creator>
      <dc:date>2017-07-28T22:29:19Z</dc:date>
    </item>
  </channel>
</rss>

