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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...