Getting Data In

All time (real-time) search through the API

zenmoto
Path Finder

I'm trying to do a real-time search using the REST API- I've got a bit of a delay indexing, and I want events as they are indexed, even if they are old. In the UI, I can specify an 'All-time (real-time)' search and get that behavior, but I can't figure out how to specify that behavior using the API. If I use earliest_time = 'rt' I seem to miss events, if I use a window like earliest_time = rt-1h I get a lot of events with preview=true and it appears they are duplicated. What is the proper earliest_time value to use for this type of search?

Tags (2)
0 Karma

zenmoto
Path Finder

I think I figured this out myself- though I'd dug into the _internal logs, inspected searches, combed through documentation and been unable to find it I just happened to be looking at my URL bar as I did an 'All time (real-time)' search in the GUI and saw the time parameters- '&earliest=rt&latest=rt'. So it looks like having both earliest_time and latest_time set to 'rt' seems to be the answer- I just need to chase down why it is working in the GUI but isn't working via the API.

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!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...