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
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!

Observability Simplified: Combining User Experience, Application Performance & ...

Tech Talk Observability Simplified: Combining User Experience, Application Performance & Network ...

Event Series May & June: From Network Visibility to Service Intelligence

Unifying the Network: Moving from Alert Noise to Service Intelligence with Splunk ITSI In today’s hybrid ...

Global Splunk User Group Events: May + June 2026

Your Splunk Community Awaits: Discover Upcoming User Group Events Worldwide    Staying ahead in the fast-paced ...