Getting Data In

Log ingestion with line level delete

bworrellZP
Communicator

This evening decided to setup a test Splunk box in my lab to goof around with.  Been a while since I have done this part of the process. (Work cluster is up and going and has been for years now).  As I was looking at my local test box, I noticed the hard drive was not likely the best size to use.

So since I have a syslog server running on this as well, and I am pulling those files into Splunk (Splunk will not always be running, hence not sending data direct to Splunk), wanted to try doing a line level destructive read.

I did see where others were using a monitor and deleting a file on ingestion, but did not see if line level was being done.

So, question is, has anyone done that, and if so, do you have some hints or pointers?

Thanks

Labels (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @bworrellZP,

you could use (only in lab) the syslog network input that doesn't write on disk.

Otherwise, use rsyslog, writing syslog on disk and then read these logs using the batch command, instead monitor, in the inputs.conf.

For more infos see at https://docs.splunk.com/Documentation/Splunk/9.2.1/Admin/Inputsconf 

In this way logs are deleted soon after ingestion.

Ciao.

Giuseppe

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!

Splunk Add-on for Microsoft Windows 11.0.3: Parse Once, Search Faster

The updated Splunk Add-on for Microsoft Windows helps customers search Windows events faster by reducing ...

What's New in Splunk Enterprise Security 8.8 and Beyond

Threats move at machine speed. Keeping up should not depend on having the biggest budget, the largest team, or ...

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...