<?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 Sourcetype in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/IIS-Sourcetype/m-p/58672#M11541</link>
    <description>&lt;P&gt;There is a work around if you choose not to re-index the log files.  You can create a new eventtype that includes all the different iis sourcetypes.  Then create a new iisFieldExtraction stanza in transforms.conf file that will be use in the props.conf to do search time field extractions.&lt;/P&gt;

&lt;P&gt;Hope that makes sense.  If not, here are some more details:&lt;/P&gt;

&lt;P&gt;Create a new eventtype called "iislogs" using the following query:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sourcetype=*_iislogs OR sourcetype=iis*
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;"iis*" is used in case your indexer appends a -1 or -2 to your iis sourcetypes.  I don't know why that's the case.  It's suppose to have stopped doing that since version 4, but mine at version 4.2.4 is still doing it.&lt;/P&gt;

&lt;P&gt;Anyway, now you have to add the following in transforms.conf file to define a generic field extraction information for your *_iislogs sourcetypes.  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[delimExtractionsIIS]
FIELDS="date","time","s-sitename","s-computername","s-ip","cs-method","cs-uri-stem","cs-uri-query","s-port","cs-username","c-ip","cs-version","cs-user-agent","cs-Cookie","cs-referer","cs-host","sc-status","sc-substatus","sc-win32-status","sc-bytes","cs-bytes","time-taken"
DELIMS = " "
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Now, create a [servername_iislogs] stanza for all the iislogs sourcetypes in props.conf that looks like the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[server1_iislogs]
REPORT-iislogs = delimExtractionsIIS

[server2_iislogs]
REPORT-iislogs = delimExtractionsIIS
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If the path to the iis log files on all the servers are identical, you can also use just a single "source" stanza for all the servers.  For example, if all your iis log files are stored on d:\logs\iislogs you can just use the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::...\\logs\\iislogs\\...\\ex*.log]
REPORT-iislogs = delimExtractionsIIS
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;From now on, all your IIS related queries must begin with &lt;CODE&gt;eventtype=iislogs&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;example:    &lt;CODE&gt;eventtype=iislogs | table s-ip, c-ip&lt;/CODE&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 26 Jan 2012 22:27:07 GMT</pubDate>
    <dc:creator>williamche</dc:creator>
    <dc:date>2012-01-26T22:27:07Z</dc:date>
    <item>
      <title>IIS Sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/IIS-Sourcetype/m-p/58671#M11540</link>
      <description>&lt;P&gt;I have several IIS servers forwarding over logs using the universal forwarder.  I modified the inputs.conf on each server creating a custom sourcetype of servername_iislogs.  The logs aren't parsing and I found out if I had set the sourcetype to IIS they would be.  If these logs are already indexed will I have to delete and re-index them with the sourcetype set to IIS in order for them to be parsed correctly?&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2012 19:39:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/IIS-Sourcetype/m-p/58671#M11540</guid>
      <dc:creator>Boell</dc:creator>
      <dc:date>2012-01-26T19:39:22Z</dc:date>
    </item>
    <item>
      <title>Re: IIS Sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/IIS-Sourcetype/m-p/58672#M11541</link>
      <description>&lt;P&gt;There is a work around if you choose not to re-index the log files.  You can create a new eventtype that includes all the different iis sourcetypes.  Then create a new iisFieldExtraction stanza in transforms.conf file that will be use in the props.conf to do search time field extractions.&lt;/P&gt;

&lt;P&gt;Hope that makes sense.  If not, here are some more details:&lt;/P&gt;

&lt;P&gt;Create a new eventtype called "iislogs" using the following query:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sourcetype=*_iislogs OR sourcetype=iis*
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;"iis*" is used in case your indexer appends a -1 or -2 to your iis sourcetypes.  I don't know why that's the case.  It's suppose to have stopped doing that since version 4, but mine at version 4.2.4 is still doing it.&lt;/P&gt;

&lt;P&gt;Anyway, now you have to add the following in transforms.conf file to define a generic field extraction information for your *_iislogs sourcetypes.  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[delimExtractionsIIS]
FIELDS="date","time","s-sitename","s-computername","s-ip","cs-method","cs-uri-stem","cs-uri-query","s-port","cs-username","c-ip","cs-version","cs-user-agent","cs-Cookie","cs-referer","cs-host","sc-status","sc-substatus","sc-win32-status","sc-bytes","cs-bytes","time-taken"
DELIMS = " "
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Now, create a [servername_iislogs] stanza for all the iislogs sourcetypes in props.conf that looks like the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[server1_iislogs]
REPORT-iislogs = delimExtractionsIIS

[server2_iislogs]
REPORT-iislogs = delimExtractionsIIS
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If the path to the iis log files on all the servers are identical, you can also use just a single "source" stanza for all the servers.  For example, if all your iis log files are stored on d:\logs\iislogs you can just use the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::...\\logs\\iislogs\\...\\ex*.log]
REPORT-iislogs = delimExtractionsIIS
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;From now on, all your IIS related queries must begin with &lt;CODE&gt;eventtype=iislogs&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;example:    &lt;CODE&gt;eventtype=iislogs | table s-ip, c-ip&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2012 22:27:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/IIS-Sourcetype/m-p/58672#M11541</guid>
      <dc:creator>williamche</dc:creator>
      <dc:date>2012-01-26T22:27:07Z</dc:date>
    </item>
    <item>
      <title>Re: IIS Sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/IIS-Sourcetype/m-p/58673#M11542</link>
      <description>&lt;P&gt;This worked,  Thanks!!&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jan 2012 16:34:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/IIS-Sourcetype/m-p/58673#M11542</guid>
      <dc:creator>Boell</dc:creator>
      <dc:date>2012-01-31T16:34:40Z</dc:date>
    </item>
    <item>
      <title>Re: IIS Sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/IIS-Sourcetype/m-p/58674#M11543</link>
      <description>&lt;P&gt;OMG!  That is truely amazing!  Thank you for putting the work in to this.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jun 2012 21:00:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/IIS-Sourcetype/m-p/58674#M11543</guid>
      <dc:creator>treinke</dc:creator>
      <dc:date>2012-06-05T21:00:16Z</dc:date>
    </item>
  </channel>
</rss>

