<?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: IIS 8.0 logfiles in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/IIS-8-0-logfiles/m-p/37785#M6937</link>
    <description>&lt;P&gt;If you run $SPLUNK_HOME/bin/splunk monitor-list show the files being monitored?  You can also check the logs on the UF to see if there are issues reported with reading the files.&lt;/P&gt;</description>
    <pubDate>Sat, 17 Aug 2013 14:30:40 GMT</pubDate>
    <dc:creator>jgedeon120</dc:creator>
    <dc:date>2013-08-17T14:30:40Z</dc:date>
    <item>
      <title>IIS 8.0 logfiles</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/IIS-8-0-logfiles/m-p/37784#M6936</link>
      <description>&lt;P&gt;I can't seem to get Splunk to injest IIS 8.0 logfiles.  I've installed a universal forwarder on a Windows Server 2012 server with IIS 8.0.  IIS is configured to log in the w3c format.   The UF is configured to monitor the IIS logfile folder.&lt;/P&gt;

&lt;P&gt;In Splunk, I can see only a few events, parsing the first two lines of the log file, which are comments and should be ignored.   The actually IIS events are not present.&lt;/P&gt;

&lt;P&gt;The source types on the events I am seeing in Splunk are "u_ex" and "iis-2".&lt;/P&gt;

&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2013 19:22:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/IIS-8-0-logfiles/m-p/37784#M6936</guid>
      <dc:creator>groundLoop</dc:creator>
      <dc:date>2013-08-16T19:22:15Z</dc:date>
    </item>
    <item>
      <title>Re: IIS 8.0 logfiles</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/IIS-8-0-logfiles/m-p/37785#M6937</link>
      <description>&lt;P&gt;If you run $SPLUNK_HOME/bin/splunk monitor-list show the files being monitored?  You can also check the logs on the UF to see if there are issues reported with reading the files.&lt;/P&gt;</description>
      <pubDate>Sat, 17 Aug 2013 14:30:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/IIS-8-0-logfiles/m-p/37785#M6937</guid>
      <dc:creator>jgedeon120</dc:creator>
      <dc:date>2013-08-17T14:30:40Z</dc:date>
    </item>
    <item>
      <title>Re: IIS 8.0 logfiles</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/IIS-8-0-logfiles/m-p/37786#M6938</link>
      <description>&lt;P&gt;If you are using Splunk 6 on both forwarder and indexer, you should try to take advantage of the headers feature we built that better understands IIS and W3C log formats.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Extractfieldsfromfileheadersatindextime"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Extractfieldsfromfileheadersatindextime&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;If you are seeing this "iis-2" sourcetype, we are attempting to use the &lt;CODE&gt;CHECK_FOR_HEADER&lt;/CODE&gt; feature which is deprecated as of Splunk 6 and never worked very well for this format.&lt;/P&gt;

&lt;P&gt;On your forwarder, you should have in inputs.conf&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;&lt;BR /&gt;
[monitor:///path-to-directory]&lt;BR /&gt;
sourcetype=iis&lt;BR /&gt;
&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Under the covers, we are using props.conf to set &lt;CODE&gt;INDEXED_EXTRACTIONS=W3C&lt;/CODE&gt; on the IIS sourcetype, ignore the first few lines of the header, and automatically map the fields found in the IIS header.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2014 20:21:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/IIS-8-0-logfiles/m-p/37786#M6938</guid>
      <dc:creator>ogdin</dc:creator>
      <dc:date>2014-02-13T20:21:49Z</dc:date>
    </item>
  </channel>
</rss>

