<?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: How to filter IIS logs on Universal Forwarder in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-IIS-logs-on-Universal-Forwarder/m-p/443065#M77199</link>
    <description>&lt;P&gt;I agree with what @chrisyoungerjds said.  Also, you should be able to do the filtering that you need inside IIS because it has extensive logging configuration features.  In fact, that is why &lt;CODE&gt;INDEXED_EXTRACTIONS&lt;/CODE&gt; was created (which is &lt;EM&gt;definitely&lt;/EM&gt; the way that you should handle IIS) because your IIS admin could change the names/orders of the fields at any time.  The whole explanation on your options can be found here:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 02 Feb 2019 17:16:19 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2019-02-02T17:16:19Z</dc:date>
    <item>
      <title>How to filter IIS logs on Universal Forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-IIS-logs-on-Universal-Forwarder/m-p/443063#M77197</link>
      <description>&lt;P&gt;Dear all,&lt;/P&gt;

&lt;P&gt;I'd like to filter IIS logs and forward only .aspx requests to Splunk. &lt;BR /&gt;
I tried something like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://C:\inetpub\logs\LogFiles\*\*.log]
 _TCP_ROUTING = default-autolb-group
 disabled = 0
 sourcetype=iis
 whitelist = (\.aspx\s)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But the "whitelist" doesn't work and forwards all log lines to Splunk.&lt;BR /&gt;
Could any one help me please?&lt;/P&gt;

&lt;P&gt;Thanks for your attention. &lt;/P&gt;</description>
      <pubDate>Sat, 02 Feb 2019 07:47:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-IIS-logs-on-Universal-Forwarder/m-p/443063#M77197</guid>
      <dc:creator>saeidsaeidsaeid</dc:creator>
      <dc:date>2019-02-02T07:47:27Z</dc:date>
    </item>
    <item>
      <title>Re: How to filter IIS logs on Universal Forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-IIS-logs-on-Universal-Forwarder/m-p/443064#M77198</link>
      <description>&lt;P&gt;Hi @saeidsaeidsaeid &lt;/P&gt;

&lt;P&gt;The whilelist in inputs.conf is only for filtering based on filename.  You will need to use this method to discard the non-asp events:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.3/Forwarding/Routeandfilterdatad#Keep_specific_events_and_discard_the_rest"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.3/Forwarding/Routeandfilterdatad#Keep_specific_events_and_discard_the_rest&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Since the &lt;CODE&gt;[iis]&lt;/CODE&gt; sourcetype uses index extractions, you should setup this props on the UF. &lt;/P&gt;

&lt;P&gt;All the best.&lt;/P&gt;</description>
      <pubDate>Sat, 02 Feb 2019 12:24:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-IIS-logs-on-Universal-Forwarder/m-p/443064#M77198</guid>
      <dc:creator>chrisyounger</dc:creator>
      <dc:date>2019-02-02T12:24:15Z</dc:date>
    </item>
    <item>
      <title>Re: How to filter IIS logs on Universal Forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-IIS-logs-on-Universal-Forwarder/m-p/443065#M77199</link>
      <description>&lt;P&gt;I agree with what @chrisyoungerjds said.  Also, you should be able to do the filtering that you need inside IIS because it has extensive logging configuration features.  In fact, that is why &lt;CODE&gt;INDEXED_EXTRACTIONS&lt;/CODE&gt; was created (which is &lt;EM&gt;definitely&lt;/EM&gt; the way that you should handle IIS) because your IIS admin could change the names/orders of the fields at any time.  The whole explanation on your options can be found here:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 02 Feb 2019 17:16:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-IIS-logs-on-Universal-Forwarder/m-p/443065#M77199</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-02-02T17:16:19Z</dc:date>
    </item>
  </channel>
</rss>

