Getting Data In

Splunk Calls for given time period

spampari
Observer

Hello Splunk Members,

Need some help on below queries,

-How many calls(read/writing) can we make in Splunk in a given time period(per second)? (Default setting in Splunk. Is it configurable? Max/Min value and how is it caluculated)
-How much data in a given time period? MB/GB? Is it changeable? Min/Max value

-How fast we can make the next insertion? Is there a delay or is it simultaneous? Would this be causing any data loss if there is any connectivity failure or downtime?

when using the Splunk enterprise in general and by using HEC method Is there any difference.

 

Thanks in Advance for

Labels (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

What do you mean by "calls"?  If you mean API calls, there is no limit I know of.

Data retrieval is not limited by time period.  Query results are limited in the amount of disk space they can use, with each role having its own configurable limit (100MB is the default).  Once the limit is reached, old jobs must be deleted to free up disk space.

Data ingestion is limited only by the power of the indexer(s).  The I/O rate of the storage system is a key factor, however.  HEC inputs tend to be faster, but have a limit of 1MB per transmission.

Data loss is possible a number of ways.  For example, if an indexer goes down and the sender does not retry the transmission then data could be lost.  We'll need to know more specifics about your environment to discuss other ways data could be lost.

---
If this reply helps you, Karma would be appreciated.
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!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...