Splunk Enterprise

Splunk Alert Manager - Not assigning status of the incident_id from "New" to "Auto_Assigned"



We are in process of upgrading our Splunk Infrastructure from ver 7.x to 8.x.

Before migration, we are stuck in the functionality testing of Alert manager ver 3.08 on Splunk Enterprise 8.1.4 (Dev env).

We are seeing that the alerts which gets triggered with Alert Manager ver 3.08, are not getting converted from "New" status to "auto_assigned".  We have checked the configurations and logs, we couldn't find anything which can give us the clarity on this issue.

Kindly help us in this issue, if you can provide alternate way to find out the root cause of this.


Note: I am attaching logs from  the Dev environment where there is no log entry of  "Set status of incident <id> to auto_assigned".



Labels (2)
Tags (1)
0 Karma
Get Updates on the Splunk Community!

Build Scalable Security While Moving to Cloud - Guide From Clayton Homes

 Clayton Homes faced the increased challenge of strengthening their security posture as they went through ...

Mission Control | Explore the latest release of Splunk Mission Control (2.3)

We’re happy to announce the release of Mission Control 2.3 which includes several new and exciting features ...

Cloud Platform | Migrating your Splunk Cloud deployment to Python 3.7

Python 2.7, the last release of Python 2, reached End of Life back on January 1, 2020. As part of our larger ...