Parameters/Results Pane: Main parameters Tab
<Prev Report Tab | Index | State conditions Tab Next> |
The Main parameters Tab is used to configure the monitoring process. It displays all the general parameters of an object currently selected in the Tree View and allows you to edit these parameters.
The Main parameters Tab contains several sections specific to the object type: either a single monitor, or a group entity: an application, host, host group, agent, monitor category, monitor type, monitor status, and root. Each section can be collapsed to save screen space; Client application remembers and restores expanded/collapsed states for a given section. Disabled or inherited parameters are shown by the appropriate font (usually grey) and background.
You can view a short help message for each parameters section clicking on the ‘?’ sign on the right of the section header:
You can modify any parameter and either save the new parameter by clicking the Save button, or revert the changes by clicking the Cancel button.
Keyboard shortcuts: Ctrl+S to save changes, and Esc to cancel.
A template group node Main Tab contains a specific section: ‘Template Monitors’. This section lists all the template monitors and allows to enable/disable them.
You can use the following template parameters (monitoring system variables) in monitor and group object parameters. Using these variables reduces configuration efforts since you can define generic parameters that expand as necessary when used in particular monitors and alerts. For example, you can use the $MonitorName variable in the SMTP monitor test message subject to simplify sorting or searching of these messages on the receiving side. In addition, these variables can be used in Alerts parameters.
Also, you can use Windows system environment variables to set monitor parameters, for example, path to a script or program for ‘Script or Program’ monitor: ‘%ProgramData%\MyDir\script.vbs’. The monitoring system resolves an environment variable as a user it is running as. By default, the monitoring service is running as LocalSystem, so it uses the LocalSystem’s Windows environment variables. These variables are specified at “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment” and at “HKEY_USERS.DEFAULT\Environment”. Make sure the variables you want to use are defined in one of those locations and they will be accessible.
Parameter inheritance
A monitor can inherit the Polling interval, Dependency settings and Credentials sections from its parent (host or application).
By default, a newly created monitor inherits these parameters from its parent host or application and most of its Monitor Definition sections are filled with the parameters stored in its Monitor Type entity. The inherited parameters cannot be edited directly: you either need to uncheck the Inherit from checkbox or edit the parent host parameters.
The given application also inherits these parameters from its parent host, the host also inherits these parameters from its parent host group; a host group inherits them from its parent Agent, and so on. Hence, it is possible to specify these parameters on any three level and to cause all the sub-tree entities to inherit them.
Note that if you change a parent host parameters, all its children that inherit this parameter, will inherit the changed value immediately.
Individual monitor parameters and group entity parameters
- Individual monitor parameters are described here.
- Group entity parameters (host groups, monitor types, monitor categories, states, and root objects) are described here.
<Prev Report Tab | Index | State conditions Tab Next> |