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
Get Updates on the Splunk Community!

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...