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 Advanced 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 that Goliath will run.
   1. For example, Windows Powershell, Command Line, etc.
   2. This must be a fully qualified program name path.
   3. In order to access the network share, the agent must have rights to the share
   4. Environment variable substitution is supported when bracketed with the percent character, for example, %SystemRoot% 
   5. Examples:
      1. Windows Powershell

         C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

      2. Command Line

         C:\Windows\system32\cmd.exe

         \\1.1.1.1\c$\temp\test.bat

6. You can optionally specify an Executable Time-Out value and Goliath 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 that will be passed to the program named in the Program Name field
   1. Please note, the parameters are case sensitive and must be upper case.
   2. Environment variable substitution is supported when bracketed with the percent character; for example, %SystemRoot%.
   3. 9 different path variables are supported as well using macro substitution. 

      1. The macro &Pn can be referenced anywhere in the string, where n is 1 through 9.

      2. The macro definition can then be defined in the GPMServer.cfg file in the Bin directory as AdvancedWatchPathn, where n is 1 through 9. For example:

         1. "AdvancedWatchPath1": "C:\\Temp\\Test1",
            "AdvancedWatchPath2": "D:\\Temp\\Test2",
            "AdvancedWatchPath3": "C:\\Temp\\Test3",
            "AdvancedWatchPath4": "C:\\Goliath\\Scripts\\Test4",
            "AdvancedWatchPath5": "C:\\Temp\\Test5",
            "AdvancedWatchPath6": "C:\\Temp\\Test6",
            "AdvancedWatchPath7": "C:\\Temp\\Test7",
            "AdvancedWatchPath8": "\\\\10.10.10.1\Test8",
            "AdvancedWatchPath9": "GDEV"

         2. Note, in the GPMServer.cfg file all backslashes must be escaped.
   4. If you are returning an Exit code from your script for processing in Goliath, please see the next step for some options surrounding how you call the script.
   5. If referencing a file, the location will be based on the machine where the execution is taking place. If the file is not local, the agent must have rights to the network share/location. 
   6. Examples: 
      1. Windows Powershell:

         "& 'C:\Program Files\MonitorIT\Scripts\test.ps1'"

         $reg = ((GP -Path 'HKLM:\SOFTWARE\Citrix\VirtualDesktopAgent\State' -Name Registered).Registered); exit $reg

         "& '\\10.20.20.20.\Scripts\test.ps1'"
         

         "& '&P2\"& '&P2\"& '&P2\"& '&P2\Scripts\test.ps1'"
         "& 'C:\Temp\&P4\Scripts\test.ps1'"
         CreateFiles.ps1'"

      2. Command Line

         net stop Spooler

8. In the Exit Code field, optionally define an exit code. When an exit code is defined, the Goliath Agent will make compare the script/programs exit code to what is defined in the rule. If the comparison fails, an alert will be generated.
   1. For example, if the Exit Code in the rule configuration is =0 but the program/script returns an exit code of 5, an alert will trigger.
   2. For Exit Codes coming back from a PowerShell script, there are two configuration options:
      
      1. Option 1 - define the Exit Code in your PowerShell using [Environment]::Exit(###) where ### is the Exit Code number you want to pass back to Goliath. 
      2. Option 2 - define the Exit Code using a powershell variable within the script, for example $exitCode = #. When using a variable for the exit code, you then want to call the variable in the Cmd-Line Options field with the following format: 
         

         "& 'c:\commands\ExitCodeTest.ps1'"; exit $exitCode

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 the location where the agent will create the process and run the executable from.
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.