Goliath Performance Monitor (GPM) Advanced Watch monitors your Windows servers/workstations by executing any Windows program, command, script, or batch file executable that you provide. It runs the executable periodically on the monitored server/workstation according to a schedule that you specify.   

Configure the Monitoring

1. To create a new monitoring condition, navigate to the Configure - Monitoring Rules page and click the New button
2. A selection pane will appear, select the radio button option for WindowsServices Watch and then click OK
3. Now the monitoring rule pane will appear. At the top of the pane name the Monitoring Rule via the Rule Name field, as well as define the description and the severity.
4. The first tab, AdvancedWatch is where you will define what is to be configured.
5. In the Program Name field, define the name of the program, Powershell, command line, batch file, etc. to be opened when the alert triggers. This must be a fully qualified program name path. In order to access the network share, the agent must have rights to the share. Environment Variable substitution when bracketed with the percent character; for example, %SystemRoot% is supported. 
   1. Examples:
      1. Powershell: powershell.exe or C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe
      2. Command or Batch file: exe or C:\Windows\system32\cmd.exe
      3. Executable: \\10.2.1.1\c$\scripts\alerts.exe
      4.  - or -  
6. You can optionally specify an Executable Time-Out value and GPM will terminate the executable if it does not complete on its own before the timeout expires.
7. In the Cmd-Line Options field, define an 'Argument' string passed to the program, batch, or command file named in the Program Name field when executed.The parameters are case sensitive and must be upper case. Environment Variable substitution when bracketed with the percent character; for example, %SystemRoot% is supported. If you are returning an Exit code from your PowerShell script for processing in Goliath Performance Monitor, please see the next step for some options surrounding how you call the PowerShell script.
   1. Examples: 
      1. Powershell: -ExecutionPolicyBypass -File "C:\Program Files\MonitorIT\Scripts\ps1" 
      2. Command Line: net stop Spooler
8. In the Exit Code field, define an exit code and a comparison that the GPM Agent will make against the executable exit code, and generate an alert if the comparison fails.
   1.  
   2. For Exit Codes coming back from a PowerShell script, you have two options.  Either define the Exit Code in your PowerShell using [Environment]::Exit(###) where ### is the Exit Code you want to pass back to Goliath Performance Monitor.
   3. 
   4. You can also alternatively use the standard Exit command instead of using [Environment]::Exit(###) in your PowerShell script by calling the script in the “Cmd-Line Options” field with the following format: 
      "& 'c:\commands\ExitCodeTest.ps1' "; exit $LASTEXITCODE
   5. 
9. The optional username and password fields are where you would, if necessary, define a user that the Goliath Agent will use to run the executable in this user’s security context.
10. In the Start Directory field, optionally specify when creating the process and running the executable.
11. Set the Show Program Window check box to have the executable window GUI appear on the screen or uncheck to run the executable in the background; hidden.