Users Guide

Field Description
Normal Select to include normal alerts.
Warning Select to include warning alerts.
Critical Select to include critical alerts.
Application Launch Configuration
Use this window to configure the application that you want to launch and to test the launch.
NOTE: Alert actions are run when a matching alert is received so the alert application launch action is a script or batch
file that does not require user interaction.
Table 189. Application Launch Configuration
Field Description
Executable Name Specifies the fully qualified path name and file name of the
executable file that launches the application program.
Arguments Specifies or edits any required or desired command line
parameters to be used in launching the application program. You
can use the following variable substitutions to specify
information in the Arguments field:
• $n = Device
• $ip = Device IP
• $m = Message
• $d = Date
• $t = Time
• $sev = Severity
• $st = Service Tag
• $r = Recommended Resolution
• $e = Enterprise OID
• $sp = Specific 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 file: If you have an executable file (for example,
createTroubleTicket.exe), to create a trouble ticket with
parameters –arg1, -arg2, and so on; configure 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 file: If you have a batch file (for example,
createTroubleTicket.bat), to create a trouble ticket with
255