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!

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...