Alerting

Alert expiration!

BserviR
Explorer

I'm currently using the token $results_link$ to get a direct link to alerts when they get triggered. I've also set the "Expires" field to 72 hrs. However, if the alerts get triggered over the weekend, the results are always expired when checking them after 48 hours. Is it possibe to have the alert results not expire in 48hrs?

Labels (1)
0 Karma
1 Solution

burwell
SplunkTrust
SplunkTrust

Hi. I think you may be hitting the dispatch.ttl setting

https://community.splunk.com/t5/Splunk-Search/What-exactly-does-the-ttl-mechanism-do/td-p/446152

Use advanced edit on your search and see what yours is set to.

View solution in original post

burwell
SplunkTrust
SplunkTrust

Hi. I think you may be hitting the dispatch.ttl setting

https://community.splunk.com/t5/Splunk-Search/What-exactly-does-the-ttl-mechanism-do/td-p/446152

Use advanced edit on your search and see what yours is set to.

BserviR
Explorer

Hi @burwell , 

Yes, this did fix my issue. I adjusted the default 2p to represent 5 days worth of time in seconds. Now when I check job manager when the alert is triggered, I see the expire time is 5 days away now.  Thanks

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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...