Monitoring Splunk

Auditing who disabled/enabled alerts on a Search Head

jeffbat
Path Finder

I am trying to figure out how I can audit who disabled alerts on one of our search heads. I was thinking it is in the _audit index but have not been able to find the information I would expect.

I have enabled the alerts again as they need to be running but I do not see an entry in audit that shows I did that even.

This is likely just a search that I am not writing correctly.

Does anyone have a search that will show me alerts that were enabled/disabled during a time period and what user performed the action?

Thanks.

Labels (2)

richgalloway
SplunkTrust
SplunkTrust

_audit doesn't have as much information as one would expect. Try looking in splunkd_ui_access.log.

---
If this reply helps you, Karma would be appreciated.

inventsekar
SplunkTrust
SplunkTrust

Hi @richgalloway 

splunkd_ui_access.log also does not have good info.. something missing, something fishy.

thanks and best regards,
Sekar

PS - If this or any post helped you in any way, pls consider upvoting, thanks for reading !
0 Karma

jeffbat
Path Finder

I am not seeing in there what user that has made a change to the specific alert. (I did see the time window where I enabled a search that was disabled but it doesn't show my account doing it, and it was only showing it through the scheduler sourcetype as that meant it got rescheduled. The only user shown is the user that the alert was created with).

This does help me narrow down when it was changed to disabled but now who did it.

Get Updates on the Splunk Community!

Observability Unlocked: Kubernetes Monitoring with Splunk Observability Cloud

 Ready to master Kubernetes and cloud monitoring like the pros? Join Splunk’s Growth Engineering team for an ...

Update Your SOAR Apps for Python 3.13: What Community Developers Need to Know

To Community SOAR App Developers - we're reaching out with an important update regarding Python 3.9's ...

October Community Champions: A Shoutout to Our Contributors!

As October comes to a close, we want to take a moment to celebrate the people who make the Splunk Community ...