Getting Data In

I noticed script alert action is officially deprecated. No easy way to setup a script triggered by log keyword?

NakatsuKinichi
Engager

The run a script alert action is officially deprecated. Create a custom alert action to package a custom script instead. Learn more
https://docs.splunk.com/Documentation/Splunk/8.0.2/AdvancedDev/CustomAlertConvertScripted

0 Karma

manjunathmeti
Champion

Hi @NakatsuKinichi,

Check my answer here to create a custom alert action with a script: https://answers.splunk.com/answers/810829/problem-with-scripted-alert.html#answer-810832

Once you create custom alert action configure alert with custom action, select Trigger condition as custom and set condition something like:

| where log_keyword <>= "match_value_ or_count"

OR

| where some conditional logic on log_keyword field values.

For more simplicity you can add conditional logic on log_keyword field values in the alert query itself and set Trigger condition to trigger when number of results is greater than 0.

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