Splunk Search

About time modifier

yuwtennis
Communicator

Hi!

I am considering to use summary index to effectively search massive data.
To do this, I am considering to set saved search and use time modifier to slide the time range ever time
the search is executed.

what I am trying to set is

earliest = @quarter-6mon latest=@quarter-3mon

I am planning to execute the above time modifier every calendar quarter.
I believe there will be a point where it is overlapped by both search.

For example,

1st search is executed at 2013/4 the time modifier will be,
2012/10/1 - 2013/1/1

Next time executed,
2013/1/1 - 2013/4/1

So 2013/1/1 is overlapped .

Would there be any way to elude this ?

Thanks,
Yu

Tags (2)
0 Karma

martin_mueller
SplunkTrust
SplunkTrust

I doubt there actually is a day of overlap, because both are pointing to midnight / 00:00 that day.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

No. Mathematically speaking, the timerange searched is the interval [earliest, latest). In other words, events occurring at the earliest timestamp are included while events occurring at the latest timestamp are not.

0 Karma

yuwtennis
Communicator

Hello martin_mueller.

Thank you for the comment.

Wouldn't events that has "2013/1/1 00:00" be overlapped?

Thanks,
Yu

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!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

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 ...