Getting Data In

Size discrepency between file system and named pipe

Branden
Builder

One of our Splunk environments receives data from a FIFO pipe. That is, syslog-ng takes incoming syslog data and sends it straight to Splunk via the pipe. It also takes incoming syslog data and writes it to the file system in the format of /logs/hostname/year/month/day/logfile

What I find odd is that if I sum up all the space used in the file system for the day, it consistency adds up to about 300-500 MB less than the amount of data that Splunk indexes for the day over the pipe.

If Splunk is receiving the same data over the pipe that is being written to the file system, how is it that it's indexing 300-500 MB more data than it's receiving?

I hope this question makes sense...

We don't have a huge license, so 300-500MB/day can make a difference. I just want to understand where it's going.

(On a side note, we're migrating to a new server, during which time we plan to lose the pipe and begin using monitor. Does that sound like a reasonable approach?)

Thanks!

Tags (2)

woodcock
Esteemed Legend

FIFOs are deprecated and unsupported so you should discontinue using them.

0 Karma

Branden
Builder

I am looking at the License Usage saved search that it comes with.

0 Karma

Stephen_Sorkin
Splunk Employee
Splunk Employee

How are you measuring the amount of data that Splunk indexed?

0 Karma
Get Updates on the Splunk Community!

Observability Unlocked: Kubernetes Monitoring with Splunk Observability Cloud

  Ready to master Kubernetes and cloud monitoring like the pros?Join Splunk’s Growth Engineering team for an ...

Wrapping Up Cybersecurity Awareness Month

October might be wrapping up, but for Splunk Education, cybersecurity awareness never goes out of season. ...

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened  Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.  In ...