Alerting

Alerts problem on 6.1.1

macewindum
Engager

Since I upgraded SPLUNK to 6.1, I have a problem with my alerts.
After few hours they stop working. I must restart SPLUNK and my alerts are back to work until they stop working.
How can I resolve that ?

Tags (3)
0 Karma

mtranchita
Communicator

Ran into this over the weekend myself. It looks to be known issue SPL-84357

The response I found at
http://answers.splunk.com/answers/137421/why-are-my-real-time-alerting-searches-no-longer-sending-em...
provided the following workaround:

The work-around is to temporarily extend "sessionTimeout" in $SPLUNK_HOME/etc/system/local/server.conf to a value that will be longer than the interval between two matched events, thus preventing the token from expiring:
[general]
sessionTimeout = 30d

0 Karma

macewindum
Engager

Thanks for the answer.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...