Getting Data In

IIS logs not recognized

rgcox1
Communicator

After uninstalling Splunk 4.0.10 and doing a clean install of 4.1.4 proxy logs not recognized:

11-10-2010 08:37:26.603 INFO  TailingProcessor - No configurations match, will ignore path='D:\logs\Web\ISALOG_20101005_WEB_000.w3c'.

Inputs.conf:

[monitor://D:\logs\web\*.w3c]
disabled = false
followtail = 1
sourcetype = isa_web
whitelist = \\logs\\*

[monitor://D:\logs\firewall\*.w3c]
disabled = true
followtail = 1
sourcetype = isa_firewall

Whitelist added per http://www.splunk.com/support/forum:SplunkAdministration/4423, but did not help. Actual case of path is D:\LOGS\Web, but changing monitor to match did not help.

Tags (1)
0 Karma

yannK
Splunk Employee
Splunk Employee

The stanza are case sensitive, the "w" of web is different in D:\logs\Web\ISALOG_20101005_WEB_000.w3c and [monitor://D:\logs\web\*.w3c]

to fix, change the stanza to [monitor://D:\logs\Web\*.w3c]

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Splunk Add-on for Microsoft Windows 11.0.3: Parse Once, Search Faster

The updated Splunk Add-on for Microsoft Windows helps customers search Windows events faster by reducing ...

What's New in Splunk Enterprise Security 8.8 and Beyond

Threats move at machine speed. Keeping up should not depend on having the biggest budget, the largest team, or ...

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...