<?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: source type identification in props.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/source-type-identification-in-props-conf/m-p/152823#M31129</link>
    <description>&lt;P&gt;As per the documentation, wildcard usage is not supported.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/MonitorfilesanddirectoriesusingtheCLI"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/MonitorfilesanddirectoriesusingtheCLI&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 11 Aug 2015 17:47:54 GMT</pubDate>
    <dc:creator>weeb</dc:creator>
    <dc:date>2015-08-11T17:47:54Z</dc:date>
    <item>
      <title>source type identification in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/source-type-identification-in-props-conf/m-p/152820#M31126</link>
      <description>&lt;P&gt;Given this in the props.conf on my indexer:&lt;/P&gt;

&lt;P&gt;[source://c:\Documents and Settings\*\AppData\Roaming\Ipswitch\WS_FTP\Logs\ws_ftp.log]&lt;BR /&gt;&lt;BR /&gt;
sourcetype = wsftp_log&lt;/P&gt;

&lt;P&gt;[source://c:\Documents and Settings\*\AppData\Roaming\Ipswitch\WS_FTP\Logs\*.rtf]&lt;BR /&gt;&lt;BR /&gt;
sourcetype = wsftp_session&lt;/P&gt;

&lt;P&gt;[wsftp_log]&lt;BR /&gt;&lt;BR /&gt;
TIME_PREFIX = ^&lt;BR /&gt;&lt;BR /&gt;
TIME_FORMAT = %Y\.%m\.%d %H:%M&lt;BR /&gt;&lt;BR /&gt;
MAX_TIMESTAMP_LOOKAHEAD = 19&lt;BR /&gt;&lt;BR /&gt;
SHOULD_LINEMERGE = FALSE&lt;BR /&gt;&lt;BR /&gt;
LINE_BREAKER = ([\n\r]+)(?=\d{4}.\d{2}.\d{2}\s\d{2}:\d{2}}&lt;BR /&gt;&lt;BR /&gt;
TRUNCATE = 99999&lt;/P&gt;

&lt;P&gt;[wsftp_session]&lt;BR /&gt;&lt;BR /&gt;
TIME_PREFIX = ^\cf2 \[&lt;BR /&gt;&lt;BR /&gt;
TIME_FORMAT = %Y\.%m\.%d %H:%M:%S\.%3N&lt;BR /&gt;&lt;BR /&gt;
SHOULD_LINEMERGE =  FALSE&lt;BR /&gt;&lt;BR /&gt;
MAX_TIMESTAMP_LOOKAHEAD = 30&lt;BR /&gt;&lt;BR /&gt;
LINE_BREAKER = ([\n\r]+)(?=^\cf2\s\[)&lt;BR /&gt;&lt;BR /&gt;
TRUNCATE = 999999&lt;/P&gt;

&lt;P&gt;When I run this:&lt;/P&gt;

&lt;P&gt;$SPLUNK_HOME\bin\splunk add oneshot "C:\documents and settings\(my user id)\Appdata\roaming\ipswitch\ws_ftp\logs\ws_ftp.log" -index testing &lt;/P&gt;

&lt;P&gt;OR&lt;/P&gt;

&lt;P&gt;$SPLUNK_HOME/bin/splunk add oneshot "C:\documents and settings\(my user id)\Appdata\roaming\ipswitch\ws_ftp\logs\salem_file1.rtf" -index testing&lt;/P&gt;

&lt;P&gt;It doesn't identify the sourcetype at all.&lt;/P&gt;

&lt;P&gt;Why?&lt;/P&gt;</description>
      <pubDate>Mon, 05 May 2014 16:02:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/source-type-identification-in-props-conf/m-p/152820#M31126</guid>
      <dc:creator>tyronetv</dc:creator>
      <dc:date>2014-05-05T16:02:20Z</dc:date>
    </item>
    <item>
      <title>Re: source type identification in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/source-type-identification-in-props-conf/m-p/152821#M31127</link>
      <description>&lt;P&gt;Maybe it has something to do with the wildcard in the source name.  Did you try specifying the sourcetype in the command?&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;$SPLUNK_HOME\bin\splunk add oneshot "C:\documents and settings\(my user id)\Appdata\roaming\ipswitch\ws_ftp\logs\ws_ftp.log" -sourcetype wsftp_log -index testing&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 May 2014 17:22:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/source-type-identification-in-props-conf/m-p/152821#M31127</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-05-05T17:22:33Z</dc:date>
    </item>
    <item>
      <title>Re: source type identification in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/source-type-identification-in-props-conf/m-p/152822#M31128</link>
      <description>&lt;P&gt;Of course I can identify the sourcetype via the command line.  The test was to check whether the props.conf on the indexer would do the identification so I can deploy an app to gather these logs from various machines and various users (hence the * in the path).&lt;/P&gt;</description>
      <pubDate>Tue, 06 May 2014 15:14:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/source-type-identification-in-props-conf/m-p/152822#M31128</guid>
      <dc:creator>tyronetv</dc:creator>
      <dc:date>2014-05-06T15:14:48Z</dc:date>
    </item>
    <item>
      <title>Re: source type identification in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/source-type-identification-in-props-conf/m-p/152823#M31129</link>
      <description>&lt;P&gt;As per the documentation, wildcard usage is not supported.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/MonitorfilesanddirectoriesusingtheCLI"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/MonitorfilesanddirectoriesusingtheCLI&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Aug 2015 17:47:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/source-type-identification-in-props-conf/m-p/152823#M31129</guid>
      <dc:creator>weeb</dc:creator>
      <dc:date>2015-08-11T17:47:54Z</dc:date>
    </item>
  </channel>
</rss>

