<?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: sourcetype best practices in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/sourcetype-best-practices/m-p/32224#M5722</link>
    <description>&lt;P&gt;I do also recommend reading &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Whysourcetypesmatter"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Whysourcetypesmatter&lt;/A&gt; and the topics that follow it.&lt;/P&gt;</description>
    <pubDate>Mon, 13 Aug 2012 21:03:14 GMT</pubDate>
    <dc:creator>ChrisG</dc:creator>
    <dc:date>2012-08-13T21:03:14Z</dc:date>
    <item>
      <title>sourcetype best practices</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sourcetype-best-practices/m-p/32220#M5718</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm looking for some help on sourcetype naming. I have a bunch of logfiles - some apache error logs, some apache access logs, some custom application error logs. I want to give my customers an easy way to search on these logs (there will be dozens of them). Should I use a pretrained source type? Wouldn't that make it more difficult to search on the logs? If I use a custom sourcetype (say "appname"), will Splunk recognize the logfile formats? &lt;/P&gt;</description>
      <pubDate>Fri, 10 Aug 2012 15:11:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sourcetype-best-practices/m-p/32220#M5718</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2012-08-10T15:11:29Z</dc:date>
    </item>
    <item>
      <title>Re: sourcetype best practices</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sourcetype-best-practices/m-p/32221#M5719</link>
      <description>&lt;P&gt;The concept of sourcetype was introduced so that a metadata field associated with an event would describe the &lt;STRONG&gt;nature&lt;/STRONG&gt; of the data, which typically tells us something about the structure of the data rather than its precise origin. "Where is this data coming from?" is a question best answered with the 'host' and 'source' metadata fields. The sourcetype is rather there to answer "What kind of data is this?".&lt;/P&gt;

&lt;P&gt;For that reason, I would not recommend to assign the same sourcetype to access logs and application logs, for example. You are probably better off using a pre-trained sourcetype whenever one is available, such as 'access_common' or 'access_combined' for HTTPD access logs. This will bring the benefit of pre-packaged field extractions, among other things.&lt;/P&gt;

&lt;P&gt;Note that most pre-trained sourcetypes are defined in &lt;CODE&gt;$SPLUNK_HOME/etc/system/default/props.conf&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 12:14:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sourcetype-best-practices/m-p/32221#M5719</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2020-09-28T12:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: sourcetype best practices</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sourcetype-best-practices/m-p/32222#M5720</link>
      <description>&lt;P&gt;Thanks, this helps me understand the usage better. Still, if I have dozens of logfiles, across multiple hosts, and I want to search them,  how would I easily do that? I don't want to type in each host or logfile - that's a lot of work. Is there an alias, or something like that?&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2012 18:00:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sourcetype-best-practices/m-p/32222#M5720</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2012-08-13T18:00:10Z</dc:date>
    </item>
    <item>
      <title>Re: sourcetype best practices</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sourcetype-best-practices/m-p/32223#M5721</link>
      <description>&lt;P&gt;There are many ways to do this, and it really depends on what qualifies the event set that you want your search to return. You can use:&lt;BR /&gt;&lt;BR /&gt;
- &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/User/StartSearching"&gt;Wildcards in your search terms&lt;/A&gt;&lt;BR /&gt;
- &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/User/ClassifyAndGroupSimilarEvents"&gt;Eventtypes&lt;/A&gt;&lt;BR /&gt;
- &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Abouttagsandaliases"&gt;Tags&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2012 20:12:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sourcetype-best-practices/m-p/32223#M5721</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2012-08-13T20:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: sourcetype best practices</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sourcetype-best-practices/m-p/32224#M5722</link>
      <description>&lt;P&gt;I do also recommend reading &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Whysourcetypesmatter"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Whysourcetypesmatter&lt;/A&gt; and the topics that follow it.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2012 21:03:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sourcetype-best-practices/m-p/32224#M5722</guid>
      <dc:creator>ChrisG</dc:creator>
      <dc:date>2012-08-13T21:03:14Z</dc:date>
    </item>
  </channel>
</rss>

