Hi @nagarjuna280,
Scripted Alert has been deprecated and it has been replaced with Custom Alert action so that's why it will be good to migrate from Scripted Alert to Custom Alert actions.
With custom alert actions you can pass different values which are not present in Splunk query output but it is require to run the script this is one of the advantage and custom alert actions runs on different framework compared to scripted alert and due to that you need to create App for custom alert actions, which contains different configuration files, html file and script.
Hi @nagarjuna280,
Scripted Alert has been deprecated and it has been replaced with Custom Alert action so that's why it will be good to migrate from Scripted Alert to Custom Alert actions.
With custom alert actions you can pass different values which are not present in Splunk query output but it is require to run the script this is one of the advantage and custom alert actions runs on different framework compared to scripted alert and due to that you need to create App for custom alert actions, which contains different configuration files, html file and script.
Hi,
you can of course just use the scripted alert action. The custom alert action is just more of a "framework concept".
For example, you have better integration in the UI, where you can configure parameters for the script. You can package the script as an app and share it via splunk base or in your environment. Those things just makes it more flexible. If you do not need this flexibility, you might have no need to use a custom alert action.
Greetings
Tom