Active Script monitors allow you to write custom VBScript or JScript code to perform specific checks on a device. If the script returns an error code, the monitor is considered down. .

Keep in mind that WhatsUp Gold does not support custom scripts; only the ability to use them in the Active Script Monitor. For more information, see Extending WhatsUp Gold with custom scripting.

Credentials are not required to run the scripts written for the Active Script Monitor. However, if the script you are writing requests credentials from a device, respective credentials are required to complete the operation.

Configure the following:

  • Name. Enter a unique name for the active monitor. This name displays in the Monitor Library.
  • Description. Enter additional information about the monitor. This description displays next to the monitor name in the Monitor Library.
  • Timeout. Enter the length of time WhatsUp Gold attempts to connect to the selected device. When the time you enter is exceeded without connecting, a timeout occurs and WhatsUp Gold stops trying to connect to the SMTP server. This is considered a failed connection.
  • Script Type. Select either VBScript or JScript.
  • Use in rescan. Select this option to have the monitor appear in the Active Monitor list on the Device Properties page. WhatsUp Gold adds the monitor type to the device during a rescan, which is started using Rescan on the Device Properties page, if the protocol or service is active on the device.
  • Use the Direct Data Access execution model. Select this option to use the Active Script Monitor execution model that was available prior to the WhatsUp Gold 16.2 SP3 release. This option may be more susceptible to Active Script monitor script errors; however, it allows you to use the Context.GetDB context object in scripts for direct interaction with the WhatsUp Gold database.
  • Use the Isolated Process execution model. Select this option to use the Active Script Monitor execution model that became available in the WhatsUp Gold 16.2 SP3 and following releases. This option may be less susceptible to Active Script monitor script errors, therefore providing more protection and stability for the WhatsUp Gold poller engine (nmservice.exe); however, it DOES NOT allow you to use the Context.GetDB context object in scripts for direct interaction with the WhatsUp Gold database.
  • Script text. Enter your monitor code in this box.