Alerting

Capability needed for 'Log event' alert action

ischoenmaker
Explorer

Does anyone know what capability to assign to a user to be able to use the 'log event' alert action?
The user has OOB power role but when he replicates one of my examples with log event action the events never reach the index. As soon as I reassign the object to my account (OOB Admin role) it works. Seems to be permission issue. From _audit log I also see the alert_actions=logevent is not even started for him:
alt text

Alternatively i can create the searches in my name and configure the log event action. I think in this way the power user can still modify the search when needed and log event will keep working.

0 Karma

mgranger1
Path Finder

In the documentation located here:

https://docs.splunk.com/Documentation/Splunk/7.2.4/Alert/LogEvents

It mentions that "Using the log event alert action requires the edit_tcp capability for users without the admin role."

I'm not positive that this will work for you, but it is certainly a place to start.

Hope this helps,
Matt Granger

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