Getting Data In

IIS Monitor causing tail errors on universal forwarder

BP9906
Builder

I added this to my inputs.conf:

[monitor://C:\WINDOWS\system32\LogFiles\W3SVC*\]
disabled = false
followTail = 0
recursive = true
index=iis
ignoreOlderThan = 7d

When the deployment server gets the deployment app and reloads, the splunkd.log on the universal forwarder errors many times this error:

04-20-2012 10:14:14.368 -0700 ERROR TailingProcessor - matching C:\WINDOWS\system32\LogFiles\Cluster\ against ^C:\\WINDOWS\\system32\\LogFiles\\W3SVC[^\\]*\\$
04-20-2012 10:14:14.368 -0700 ERROR TailingProcessor - matching C:\WINDOWS\system32\LogFiles\HTTPERR\ against ^C:\\WINDOWS\\system32\\LogFiles\\W3SVC[^\\]*\\$

How do I get rid of this repeat error message?

0 Karma
1 Solution

BP9906
Builder

I found this to work the best.

[monitor://C:\WINDOWS\system32\LogFiles\*\*.log]

disabled = false
followTail = 0
recursive = true
index=iis
ignoreOlderThan = 7d
sourcetype=MSWindows:2003:IIS

[monitor://C:\inetpub\logs\LogFiles\*\*.log]
disabled = false
followTail = 0
recursive = true
index=iis
ignoreOlderThan = 7d
sourcetype=MSWindows:2008R2:IIS

View solution in original post

0 Karma

BP9906
Builder

I found this to work the best.

[monitor://C:\WINDOWS\system32\LogFiles\*\*.log]

disabled = false
followTail = 0
recursive = true
index=iis
ignoreOlderThan = 7d
sourcetype=MSWindows:2003:IIS

[monitor://C:\inetpub\logs\LogFiles\*\*.log]
disabled = false
followTail = 0
recursive = true
index=iis
ignoreOlderThan = 7d
sourcetype=MSWindows:2008R2:IIS

0 Karma

BP9906
Builder

I resolved it by removing the wildcard char. It must be a splunk forwarder error to repeat the error in the log.

ie

[monitor://C:WINDOWS\system32\LogFiles] 
disabled = false 
followTail = 0 
recursive = true 
index=iis 
ignoreOlderThan = 7d
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...