Can SAM provide variables to a script?

Question

A desire of the Engineering team that I am a member of is to create a single script that can be re-used for the same purpose, but on different managed nodes. This script is a simple "service restart" script with basic parameters set to identify the computer name and service name. An example of this is to call said script to restart a service. The service/computer names would vary per alert that is triggered, which would require different values to be set as parameters within the script itself.

The "execute and external script" alert trigger action only allows the user to provide the path to the script document. A question that I have is..does SAM have the ability to provide necessary parameter details (computer/service name) to be used by a pre-existing batch file?

michael_malendoski · Answer

Much thanks to you all for the input! Will be working with the Powershell gurus at my place of employment to get some automation implemented in our alerts.

jangliss · Answer

These work perfectly when doing arguments to scripts for SAM to be monitoring.  Based on the question being about restarting services, the question was more about the event actions in alerting.

jdumke · Answer

I used a Windows PowerShell Monitor to pass parameters:

Script Arguments:

${IP},443,tcp

Script Body Snippet:

#Get credentials, start remote session and import commands from that session

#Get the IP of the current node as the first argument passed to the script

$IP = $args[0]

$Port = $args[1]

$Protocol = $args[2]

echo "IP: $($IP)"

echo "Port: $($Port)"

echo "Protocol: $($Protocol)"