Getting Data In

How to ingest large volume of data to Splunk via REST API call without pagination?

arjitg
Explorer

Hi Team! I need to make a REST API GET call to ingest a fairly large amount of data to splunk and unfortunately, this REST API doesn't have a pagination logic. So, it literally dumps an entire set of some 50,000 records every time. So may I know which can be the best way to ingest only new data into Splunk? Is there any best practices to ingest only delta records (which are new) to the system? Thanks.   

0 Karma
1 Solution

isoutamo
SplunkTrust
SplunkTrust

Hi

Are you writing a modular inputs? If so, you should add a checkpoint method for bookkeeping what you have already ingesting and what is the next one.

If you are asking something else, then you must clarify your question.

r. Ismo

View solution in original post

arjitg
Explorer

Thanks @isoutamo! Yeah So this is a scripted input but certainly, I can implement the checkpoint logic to this solution. 

0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

Are you writing a modular inputs? If so, you should add a checkpoint method for bookkeeping what you have already ingesting and what is the next one.

If you are asking something else, then you must clarify your question.

r. Ismo

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!

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...

Pro Tips for .conf26: How to Prep Like a Splunk Veteran

There’s no shortage of incredible content lined up for .conf26 in Denver, from deep-dive technical sessions ...