Splunk Search

All Time Search Earliest Workload

sle
Engager
<search>

<query>index="ourIndex"  sourcetype=$stype$ABC AND Is_Service_Account="True" OR Is_Service_Account="False"  earliest=-48h | eval DC=upper(DC) |  eval env1=case(DC like "%Q%","QA", DC like "%DEV%","DEV", true(), "PROD")  | search env1=$envPure$ AND $domainPure$ |rename DC AS domainPure | stats count </query>


<earliest>0</earliest>


<latest></latest>


</search>

 

If earliest=-48h and within the source code there is <earliest>0</earliest>, then if we enable an admission rule that disables All Time searches what would happen? 

Tags (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @sle ,

if you use earliest and/or latest fields in your main search, this value override the values that you have in the Time Picker, that's not relevant.

Ciao.

Giuseppe

gcusello
SplunkTrust
SplunkTrust

Hi @sle,

good for you, see next time!

let me know if I can help you more, or, please, accept one answer for the other people of Community.

Ciao and happy splunking

Giuseppe

P.S.: Karma Points are 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!

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...

Trusted Autonomy in the SOC: A Maturity Journey

AI is compressing attacker timelines and pushing SOC teams beyond human capacity thresholds. The next SOC ...

Supercharging Windows Security Detection Performance: Introducing Hybrid Field ...

Windows event logs—from Security auditing and Sysmon to PowerShell script blocks—form the operational backbone ...