Splunk Search

Saved searches lifetime: difference between dispatch.ttl and alert.expires in savedsearches.conf

BernardEAI
Communicator

I'm trying to accurately control the lifetime of the search artifacts of a saved search. I have set the "Expiry" time to 30 mins in the saved search, but if I check the artifacts in the  "Jobs" view, the expiry of the search is 2 hours after start.

Looking at the savesdearches.conf I see the item "alert.expires = 30m" in the saved search stanza. I have also seen the item "dispatch.ttl" in the Spunk documentation for savedsearches.conf, where it states:

dispatch.ttl = <integer>[p]
* Indicates the time to live (ttl), in seconds, for the artifacts of the
  scheduled search, if no actions are triggered.

 According to that the life of the artifacts is controlled by this parameter. What does alert.expires control? Is there a way to set dispatch.ttl via the UI?

Labels (1)
Tags (1)
0 Karma
1 Solution

BernardEAI
Communicator

I found the answer to the question: the "dispatch.ttl" can be configured in the "Advanced Edit" of the saved search.

View solution in original post

0 Karma

BernardEAI
Communicator

I found the answer to the question: the "dispatch.ttl" can be configured in the "Advanced Edit" of the saved search.

View solution in original post

0 Karma

gjanders
SplunkTrust
SplunkTrust

Because non-admins couldn't always see the advanced edit I created an app / code here https://github.com/gjanders/SplunkOther so that they could change the TTL of there own alerts without hitting the REST API...

Alerts for Splunk Admins https://splunkbase.splunk.com/app/3796/
Version Control for Splunk https://splunkbase.splunk.com/app/4355/
0 Karma
Register for .conf21 Now! Go Vegas or Go Virtual!

How will you .conf21? You decide! Go in-person in Las Vegas, 10/18-10/21, or go online with .conf21 Virtual, 10/19-10/20.