Getting Data In

Lots of WinEventLogChannel -subscribeToEvtChannel

elusive
Splunk Employee
Splunk Employee

There are a lot of these error messages logged in splunkd.log

09-23-2010 09:31:28.062 ERROR WinEventLogChannel - subscribeToEvtChannel: Could not subscribe to Windows Event Log channel 'Microsoft-Windows-TaskScheduler/Diagnostic', 'The caller is trying to subscribe to a direct channel which is not allowed. The events for a direct channel go directly to a logfile and cannot be subscribed to.'.
09-23-2010 09:31:28.062 ERROR WinEventLogChannel - init: Init failed, unable to subscribe to Windows Event Log channel 'Microsoft-Windows-TaskScheduler/Diagnostic':
09-23-2010 09:31:28.062 ERROR WinEventLogInputProcessor - main-thread: Failed to initialize Windows Event Log 'Microsoft-Windows-TaskScheduler/Diagnostic'

elusive
Splunk Employee
Splunk Employee

Not all Windows Event log collection that appears in Manager » Data inputs » Event log collections » localhost can be subscribed. Check Microsoft Site

Also, please note, Splunk has a threshold of 63 that you can select from Available logs. Selecting more than threshold limit will cause problem. In other words, do not add all.

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!

Tuning Edge Processor in Hybrid Mode: What Limits Each Data Path

When you run Edge Processor in hybrid mode, alongside a Splunk heavy forwarder on the same host, two questions ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Request for Professional Development: Attending .conf26

Winning Over the Boss: Your Pass to .conf26 conf26 is going to be here before you know it. If don't already ...