<?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 rename for IIS logs on default sites in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Source-rename-for-IIS-logs-on-default-sites/m-p/65658#M96932</link>
    <description>&lt;P&gt;Fervin,&lt;/P&gt;

&lt;P&gt;Great question.  I have had the same issue, which is, that different physical servers can have the same siteid and therefore all get lumped in with the same source.&lt;/P&gt;

&lt;P&gt;I have also implemented your proposed solution at several sites and it works very well.&lt;/P&gt;

&lt;P&gt;I created an app called TA-iss to deal with this (TA=Technology-Addon a splunk term for apps that do these sorts of extractions/manipulation).  This does index-time manipulation and therefore it should go on whatever system does your parsing (e.g. the forwarder if you are using anything but a Universal Forwarder, or the Indexer if you send directly to the indexer from a Universal Forwarder).&lt;/P&gt;

&lt;P&gt;In the &lt;EM&gt;props.conf&lt;/EM&gt; for IIS logs, I have this line:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TRANSFORMS-force_source_for_iis = force_source_for_iis
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And the referenced stanza in &lt;EM&gt;transforms.conf&lt;/EM&gt; looks like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[force_source_for_iis]
DEST_KEY = MetaData:Source
REGEX = \d{2}\:\d{2}\s+([^\ ]*)\s+([^\ ]*)
FORMAT = source::$2-$1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This makes each source unique to the &lt;EM&gt;host-site_id&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;Best,&lt;BR /&gt;
Sean&lt;/P&gt;</description>
    <pubDate>Thu, 24 Nov 2011 13:17:08 GMT</pubDate>
    <dc:creator>sdwilkerson</dc:creator>
    <dc:date>2011-11-24T13:17:08Z</dc:date>
    <item>
      <title>Source rename for IIS logs on default sites</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-rename-for-IIS-logs-on-default-sites/m-p/65656#M96930</link>
      <description>&lt;P&gt;Hello,  &lt;/P&gt;

&lt;P&gt;I've noticed an issue with IIS logs that are being written from sites with a default site ID such as (...\logfiles\W3SVC1\ex110826.log).  Logs from sites with random site IDs work perfectly fine.&lt;/P&gt;

&lt;P&gt;The issue is that logs from these sites all get lumped together when the application builds its summaries.&lt;/P&gt;

&lt;P&gt;Changing site IDs across the environment would be a less than ideal approach to fixing this behavior.&lt;/P&gt;

&lt;P&gt;Would it be possible to rename these sources at index time and substitute a machine specific element into the source name?  It would be perfect if I could transform \logfiles\W3SVC1\ to \logfiles\W3SVC#SERVERNAME or something.&lt;/P&gt;

&lt;P&gt;If not, are there any other ways around this?  Thanks in advance,&lt;/P&gt;

&lt;P&gt;-Frank&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2011 15:48:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-rename-for-IIS-logs-on-default-sites/m-p/65656#M96930</guid>
      <dc:creator>fervin</dc:creator>
      <dc:date>2011-08-26T15:48:47Z</dc:date>
    </item>
    <item>
      <title>Re: Source rename for IIS logs on default sites</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-rename-for-IIS-logs-on-default-sites/m-p/65657#M96931</link>
      <description>&lt;P&gt;That seems like a good enhancement request for the app - essentially, facilitate a mapping of the tuple machine-site id-site name.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Aug 2011 17:38:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-rename-for-IIS-logs-on-default-sites/m-p/65657#M96931</guid>
      <dc:creator>araitz</dc:creator>
      <dc:date>2011-08-29T17:38:24Z</dc:date>
    </item>
    <item>
      <title>Re: Source rename for IIS logs on default sites</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-rename-for-IIS-logs-on-default-sites/m-p/65658#M96932</link>
      <description>&lt;P&gt;Fervin,&lt;/P&gt;

&lt;P&gt;Great question.  I have had the same issue, which is, that different physical servers can have the same siteid and therefore all get lumped in with the same source.&lt;/P&gt;

&lt;P&gt;I have also implemented your proposed solution at several sites and it works very well.&lt;/P&gt;

&lt;P&gt;I created an app called TA-iss to deal with this (TA=Technology-Addon a splunk term for apps that do these sorts of extractions/manipulation).  This does index-time manipulation and therefore it should go on whatever system does your parsing (e.g. the forwarder if you are using anything but a Universal Forwarder, or the Indexer if you send directly to the indexer from a Universal Forwarder).&lt;/P&gt;

&lt;P&gt;In the &lt;EM&gt;props.conf&lt;/EM&gt; for IIS logs, I have this line:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TRANSFORMS-force_source_for_iis = force_source_for_iis
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And the referenced stanza in &lt;EM&gt;transforms.conf&lt;/EM&gt; looks like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[force_source_for_iis]
DEST_KEY = MetaData:Source
REGEX = \d{2}\:\d{2}\s+([^\ ]*)\s+([^\ ]*)
FORMAT = source::$2-$1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This makes each source unique to the &lt;EM&gt;host-site_id&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;Best,&lt;BR /&gt;
Sean&lt;/P&gt;</description>
      <pubDate>Thu, 24 Nov 2011 13:17:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-rename-for-IIS-logs-on-default-sites/m-p/65658#M96932</guid>
      <dc:creator>sdwilkerson</dc:creator>
      <dc:date>2011-11-24T13:17:08Z</dc:date>
    </item>
  </channel>
</rss>

