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!

Network to App: Observability Unlocked [May & June Series]

In today’s digital landscape, your environment is no longer confined to the data center. It spans complex ...

SPL2 Deep Dives, AppDynamics Integrations, SAML Made Simple and Much More on Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...