Splunk Search

When will ad-hoc search artifacts/results be deleted?

peterschloenske
Explorer

Hi,

I am wondering when my search artifacts/shown results will be deleted.
Default ttl for ad-hoc searches is 10min. I would expect the results of my opened & completed search to disappear after this time. Currently they don't and the expiration time is updated every time I refresh the jobs manager.

Cheers

Tags (2)
0 Karma
1 Solution

harsmarvania57
Ultra Champion

Hi,

Yes, you are correct default ttl for ad-hoc search is 10min but if job is actively viewed in Splunk UI then status.csv file changes mod-time continuously and due to that in Job Manager expire time increase at every time when you refresh job manager & job will not delete from dispatch directory.

ttl = <integer>
* How long, in seconds, the search artifacts should be stored on disk after
  the job completes. The ttl is computed relative to the modtime of the
  status.csv file of the job, if the file exists, or the modtime of the
  artifact directory for the search job.
* If a job is being actively viewed in the Splunk UI then the modtime of
  the status.csv file is constantly updated such that the reaper does not
  remove the job from underneath.
* Default: 600 (10 minutes)

View solution in original post

0 Karma

harsmarvania57
Ultra Champion

Hi,

Yes, you are correct default ttl for ad-hoc search is 10min but if job is actively viewed in Splunk UI then status.csv file changes mod-time continuously and due to that in Job Manager expire time increase at every time when you refresh job manager & job will not delete from dispatch directory.

ttl = <integer>
* How long, in seconds, the search artifacts should be stored on disk after
  the job completes. The ttl is computed relative to the modtime of the
  status.csv file of the job, if the file exists, or the modtime of the
  artifact directory for the search job.
* If a job is being actively viewed in the Splunk UI then the modtime of
  the status.csv file is constantly updated such that the reaper does not
  remove the job from underneath.
* Default: 600 (10 minutes)
0 Karma
Get Updates on the Splunk Community!

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...