Getting Data In

Universal Forwarder requires restart after registering new WinEventLog source

HumanPrinter
Explorer

We are running a Universal Forwarder on our Windows servers which host several of our application. Each application logs to the same Windows Event Logbook, but use different sources to be able to determine the source of the logging.
We have configured the UF to forward all messages from the logbook to the heavy forwarders according to the inputs.conf-snippet below:

[WinEventLog://ServerApps]
disabled = 0
sourcetype = ServerAppLogs
source = ServerApp
renderXml = false

The problem is, whenever a new application is deployed, it will register a new source with the Windows Event logbook (using Powershell: [System.Diagnostics.EventLog]::CreateEventSource($eventSourceName, $eventLogName)). But the UF does not pick up this new source untill it is restarted even though we did not specify any whitelisting or blacklisting.

Is it possible to make the UF listen to new sources in the Windows Event Log without having to restart it?

PS. We are using version 7.3.1 of the Universal Forwarder

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...