Alerting

Getting a cannot find viewstate when disabling alerts

lanilim16
Explorer

I'm a admin user and when I try to disable any alert

I get an error similar to the one blelow
In handler 'savedsearch': Cannot find viewstate with vsid="gle4xmxd"

Tags (3)
0 Karma
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

Sounds like a broken link from times gone by... go to that savedsearches.conf and remove the line vsid=gle4xmxd from that saved search's stanza.

View solution in original post

martin_mueller
SplunkTrust
SplunkTrust

Sounds like a broken link from times gone by... go to that savedsearches.conf and remove the line vsid=gle4xmxd from that saved search's stanza.

martin_mueller
SplunkTrust
SplunkTrust

After editing .conf files manually you will need to either restart splunk or hit http://splunk_host:port/debug/refresh?entity=saved/search to tell splunk about the changed file.

There will be no impact because the viewstate apparently doesn't exist any more. Can't lose something that's already gone.

0 Karma

lanilim16
Explorer

awesome thanks, this actually worked the URL is http://splunk_host:port/debug/refresh?entity=admin/savedsearch to do a refresh without restart

0 Karma

lanilim16
Explorer

I already removed this from savedsearches.conf beforehand and still get the same error, am I supposed to restart the app for this to take effect? Further to this all alerts are actually resulting to this error message, so if I remove this, will there be any impact?

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!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...