Getting Data In

Splunk Add-on Builder REST data input pagination

yotamcp
Engager

Hi,

I've recently started working with the Splunk Add-on Builder to quickly query and index data from a REST API of one of my systems.

The response looks something like this:

 

{
"count":296,
"next":"http://mysite.com/api/?page=2&page_size=200",
"previous":null,
"results": [...]
}

 

I was wondering if there is a way to paginate through the results.

Note: I am aware of checkpoints (I'm using this as well), but am looking for something else.

The behavior I'm looking for is a paginated query, that will continue until "next=null", and then sleep for the specified interval of the data input. 

Any ideas? (I would really prefer not implementing a whole new REST client, when there is already a really good implementation here)

Thanks!

  

Labels (1)

Tyler
Explorer

The REST data input is quite simple. You'll have to code in order to get it to pull more pages.

This would be a good feature request. I don't see it being difficult to implement.

0 Karma

kfennell
Engager

Working through the same issue here. I'm wondering if I have to script it myself so it loops through requests until there are no more results. Seems like something that would be common, so I am still thinking there must be configurable way....

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!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...