Getting Data In

Need assistance getting large data into Splunk

nls7010
Path Finder

This is a note my client sent:

I can’t really use the logs from Splunk, because they are spotty.. Think I figured out why it’s missing data though.  From our last meeting, they bumped up the transfer rate from 1024KBps to 2048KBps because the CE was generating too much data.  However, the CE raw logs generate roughly about 75MB/Minute or 1.25MBps raw.  Since Splunk does use compression at ~17%, the 2KBps gets you about 11KBps raw.  The 1.25MBps is roughly 217.6KBps compressed.  Hence, it gives you roughly 5% of the total logs.  To support Openway and prevent dropping any logs, we need to set a conservative rate to handle 110MB/minute raw, which would be ~319KBps.

We did set in the limits.conf to the 2048 mentioned above, but we're not certain how to set to a level the client needs.

Labels (1)
Tags (1)
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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...