Getting Data In

Universal Forwarder - Start collection without indexing old logs

zindain24
Path Finder

Hello, we are looking to collect Windows (Application, Security, and System) logs from 14 Domain Controllers. By default the Universal Forwarder begins indexing the logs from the systems earliest event to the most recent. Is there a way we can tell the forwarder to start collection of new events, and not index the old log files?

Thanks!

0 Karma
1 Solution

ysouchon
Explorer

Via inputs.conf (local): current_only = 1

or

Via wmi.conf (remote) : current_only = 1

View solution in original post

0 Karma

criazuelo_splun
Splunk Employee
Splunk Employee

This solution didn't work with a UF v 7.3.2 and Windows Server 2012R2 standard.

0 Karma

zindain24
Path Finder

Thanks ysouchon, added the following to inputs.conf:

[WinEventLog:Security]
disabled = 0
start_from = oldest
current_only = 1
index = indexname

[WinEventLog:System]
disabled = 0
start_from = oldest
current_only = 1
index = indexname

[WinEventLog:Application]
disabled = 0
start_from = oldest
current_only = 1
index = indexname

0 Karma

ysouchon
Explorer

Via inputs.conf (local): current_only = 1

or

Via wmi.conf (remote) : current_only = 1

0 Karma

criazuelo_splun
Splunk Employee
Splunk Employee

This solution didn't work with a UF v 7.3.2 and Windows Server 2012R2 standard.

0 Karma
Get Updates on the Splunk Community!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...