<?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 How does rule based sourcetype works? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-does-rule-based-sourcetype-works/m-p/110805#M183598</link>
    <description>&lt;P&gt;In the below stanzas , both are having same source-type names, how the priority will be in assigning sourcetype?&lt;/P&gt;

&lt;P&gt;Has anybody used rule based sourcetype, any example will be more useful.&lt;/P&gt;

&lt;P&gt;in the beloe case &lt;CODE&gt;"MORE_THAN_75"&lt;/CODE&gt; means no. of events ?&lt;/P&gt;

&lt;P&gt;Normal sourcetype : &lt;STRONG&gt;access_combined&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[access_combined]
pulldown_type = true
maxDist = 28
MAX_TIMESTAMP_LOOKAHEAD = 128
REPORT-access = access-extractions
SHOULD_LINEMERGE = False
TIME_PREFIX = \[
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;Rule Based&lt;/STRONG&gt; Sourcetype : access_combined&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[rule::access_combined]
sourcetype = access_combined
MORE_THAN_75 = ^\S+ \S+ \S+ \S* ?\[[^\]]+\] "[^"]*" \S+ \S+ \S+ "[^"]*"$
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 19 Jun 2014 10:09:25 GMT</pubDate>
    <dc:creator>splunker12er</dc:creator>
    <dc:date>2014-06-19T10:09:25Z</dc:date>
    <item>
      <title>How does rule based sourcetype works?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-does-rule-based-sourcetype-works/m-p/110805#M183598</link>
      <description>&lt;P&gt;In the below stanzas , both are having same source-type names, how the priority will be in assigning sourcetype?&lt;/P&gt;

&lt;P&gt;Has anybody used rule based sourcetype, any example will be more useful.&lt;/P&gt;

&lt;P&gt;in the beloe case &lt;CODE&gt;"MORE_THAN_75"&lt;/CODE&gt; means no. of events ?&lt;/P&gt;

&lt;P&gt;Normal sourcetype : &lt;STRONG&gt;access_combined&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[access_combined]
pulldown_type = true
maxDist = 28
MAX_TIMESTAMP_LOOKAHEAD = 128
REPORT-access = access-extractions
SHOULD_LINEMERGE = False
TIME_PREFIX = \[
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;Rule Based&lt;/STRONG&gt; Sourcetype : access_combined&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[rule::access_combined]
sourcetype = access_combined
MORE_THAN_75 = ^\S+ \S+ \S+ \S* ?\[[^\]]+\] "[^"]*" \S+ \S+ \S+ "[^"]*"$
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 19 Jun 2014 10:09:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-does-rule-based-sourcetype-works/m-p/110805#M183598</guid>
      <dc:creator>splunker12er</dc:creator>
      <dc:date>2014-06-19T10:09:25Z</dc:date>
    </item>
    <item>
      <title>Re: How does rule based sourcetype works?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-does-rule-based-sourcetype-works/m-p/110806#M183599</link>
      <description>&lt;P&gt;Hi splunker12er,&lt;/P&gt;

&lt;P&gt;the docs provide nice examples &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.1/Data/Configurerule-basedsourcetyperecognition#Examples"&gt;http://docs.splunk.com/Documentation/Splunk/6.1.1/Data/Configurerule-basedsourcetyperecognition#Examples&lt;/A&gt;  about rule based sourcetype assignment.&lt;/P&gt;

&lt;P&gt;Related to your example this means, if 75% or more of the input lines match the regex, then this sourcetype will be used.&lt;/P&gt;

&lt;P&gt;Cheers, MuS&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jun 2014 11:56:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-does-rule-based-sourcetype-works/m-p/110806#M183599</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2014-06-19T11:56:47Z</dc:date>
    </item>
  </channel>
</rss>

