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!

Splunk MCP & Agentic AI: Machine Data Without Limits

  Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization ...

Finding Based Detections General Availability

Overview  We’ve come a long way, folks, but here in Enterprise Security 8.4 I’m happy to announce Finding ...

Get Your Hands Dirty (and Your Shoes Comfy): The Splunk Experience

Hands-On Learning and Technical Seminars  Sometimes, you just need to see the code. For those looking for a ...