Users Guide

Field Description
• $sev = Severity
• $st = Service Tag
• $r = Recommended Resolution
• $e = Enterprise OID
• $sp = Specic trap ID
• $g = Generic trap ID
• $cn = Alert Category Name
• $sn = Alert Source Name
• $pkn = Package Name
• $at = Asset Tag
• $loc = Device Location
• $mod = Model Name
Executable le: If you have an executable le (for example,
createTroubleTicket.exe), to create a trouble ticket with
parameters –arg1, -arg2, and so on; congure the alert
application launch as follows:
• Executable Name (with the full path): C:\temp
\createTroubleTicket.exe
• Argument: -arg1 –arg2
When the alert action is triggered, it runs the command C:\temp
\createTroubleTicket.exe –arg1 -arg2 to perform the associated
application launch alert action.
Batch le: If you have a batch le (for example,
createTroubleTicket.bat), to create a trouble ticket with
parameters –arg1, -arg2, and so on, congure the alert
application launch as follows:
• Executable Name (with the full path): C:\temp
\createTroubleTicket.bat
• Argument: -arg1 –arg2
When the alert action is triggered, it runs the command C:\temp
\createTroubleTicket.bat –arg1 -arg2 to perform the associated
application launch alert action.
VB script: When conguring vb script les as an alert action,
provide the executable and arguments as follows. For example,
if you have a script (createTroubleTicket.vbs), to create a trouble
ticket that contains one parameter arg1, congure the
application launch as follows:
• Executable Name: cscript.exe or C:\Windows
\System32\cscript.exe (full path)
• Argument: C:\temp\createTroubleTicket.vbs arg1
When the alert action is triggered, it runs the command
cscript.exe C:\temp\ createTroubleTicket.vbs arg1 to perform
the associated application launch alert action.
NOTE: If an alert action is not working, ensure that you
have entered complete command from the command
prompt.
See the sample alert action under Application Launch alert
action for more information.
Test Action
Allows you to test the application launch.
269