Getting Data In

IIS 8.0 logfiles

groundLoop
New Member

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.

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.

The source types on the events I am seeing in Splunk are "u_ex" and "iis-2".

Thanks in advance.

Tags (2)
0 Karma

ogdin
Splunk Employee
Splunk Employee

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.

http://docs.splunk.com/Documentation/Splunk/latest/Data/Extractfieldsfromfileheadersatindextime

If you are seeing this "iis-2" sourcetype, we are attempting to use the CHECK_FOR_HEADER feature which is deprecated as of Splunk 6 and never worked very well for this format.

On your forwarder, you should have in inputs.conf


[monitor:///path-to-directory]
sourcetype=iis

Under the covers, we are using props.conf to set INDEXED_EXTRACTIONS=W3C on the IIS sourcetype, ignore the first few lines of the header, and automatically map the fields found in the IIS header.

0 Karma

jgedeon120
Contributor

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.

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...