| \n\nHealth monitor script\n\n | \n\nUsed by a monitor to:\n\n |
|---|---|
| \n\nCheck delay in event processing\n\n | \n\nMonitor the duration of events \\[in minutes\\] that remain in Ready state and are not processed.\n\n |
| \n\nConnectors Monitor\n\n | \n\nMonitor:- Whether the time that a connector in idle state surpassed the threshold \\[in minutes\\] configured.\n- The active status of connectors.\n\n |
| \n\nGet Event Processing state\n\n | \n\nMonitor the time that events are in Ready state. Alerts are sent when this time exceeds the threshold.\n\n |
| \n\nMID Server Threshold Alerts\n\n | \n\nMonitor MID Server health. Events are sent when changes in MID Server state are detected.\n\n |
| \n\nMonitor\n\n | \n\nDescription\n\n |
|---|---|
| \n\nConnector's idle state monitoring\n\n | \n\nMonitor to verify whether any of the connectors were in idle state that surpassed the threshold \\[in minutes\\] that was configured.Health Monitor script selected: `Connectors Monitor`.\n\n |
| \n\nConnectors Status\n\n | \n\nMonitor to track the active status of the connectors. Select only one threshold to configure which severity to invoke using 1 to select the threshold field or 0 to ignore the threshold field. For more information, see [Connector status example](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/configure-threshold-monitoring.md). Health Monitor script selected: `Connectors Monitor`.\n\n |
| \n\nDelay in event processing\n\n | \n\nMonitor to track the duration of events \\[in minutes\\] that remain in Ready state and were not processed. This duration period initiates an alert for the event processing CI with severity according to the configured thresholds \\[minutes\\].Health Monitor script selected: `Check delay in event processing`.\n\n |
| \n\nEvent Processing job\n\n | \n\nMonitor the state of the event processing jobs. An alert is generated when the idle time of a job exceeds the configured threshold.Health Monitor script selected: `Get Event Processing state`.\n\n |
| \n\nMID Server MID Server Threshold Alerts\n\n | \n\nMonitor MID Server MID Server health. Events are sent when issues with MID Server availability and resource thresholds are detected.Health Monitor script selected: `MID Server Threshold Alerts`.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nName\n\n | \n\nDescriptive and meaningful name for the monitor.\n\n |
| \n\nDescription\n\n | \n\nText narrative that describes the monitor.\n\n |
| \n\nActive\n\n | \n\nCheck box to enable the monitor.\n\n |
| \n\nMonitoring job frequency \\[seconds\\]\n\n | \n\nFrequency that the monitoring job should run. Default: `120` seconds.\n\n |
| \n\nLast Run\n\n | \n\nLast run date and time. These values are automatically updated.\n\n |
| \n\nScript\n\n | \n\nMonitoring script. Click the search icon. The existing scripts are listed in the Health Monitor Scripts screen, or click **New** to create a custom health monitor script. For more information about creating a custom health monitor script, see step [3](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/custom-configure-threshold-monitoring.md).\n\n |
| \n\n**Note:** Regarding all the following threshold configuration fields: All monitored values are compared against the thresholds. If a monitored value exceeds a threshold, an alert with the appropriate severity is issued.\n\n | |
| \n\nCritical Threshold\n\n | \n\nAny point above the value is considered a critical consequence.\n\n |
| \n\nMajor Threshold\n\n | \n\nAny point above the value, but below the value of the Critical Threshold, is considered a major consequence.\n\n |
| \n\nMinor Threshold\n\n | \n\nIf exceeded, the value is considered a minor consequence.\n\n |
| \n\nWarning Threshold\n\n | \n\nIf the value is exceeded, a warning is issued.\n\n |
| \n\nAdditional information\n\n | \n\nFurther information about the monitor.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nActive\n\n | \n\nCheck box to enable the monitor.\n\n |
| \n\nDescription\n\n | \n\nText narrative that describes the custom script.\n\n |
| \n\nName\n\n | \n\nDescriptive and meaningful name for the custom script.\n\n |
| \n\nScript\n\n | \n\nCustom script to run when called from a monitor. A script template is provided as a guide. You can use the [Health monitor scripts provided with the base system](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/custom-configure-threshold-monitoring.md) as examples of how to author the script, and use the [script editor tools](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/scripts/c_SyntaxEditor.md).\n\nEnsure that the custom script includes:Run the monitor function, which is called according to the \"monitoring job frequency” setting **runUpdateHealthMonitorScripts\\(scriptId\\)**. Add this function to run the monitoring logic.\n\n Specify the configuration function that is called every hour **runInsertHealthMonitorScripts\\(scriptId\\)**. Add the configuration logic and add a CI if needed. In the navigation pane search field, enter `em_monitor_state.list`. In the Monitoring States \\[em\\_monitor\\_state\\] table, specify the initialization of the monitor record in the required record.\n\n Use the helper functions defined in **EvtMgmtHealthMonitorCommon** and **EvtMgmtEventAlertGenerator** script includes:\n\n - EvtMgmtHealthMonitorCommon\n- healthMonitorCommon.shouldRun\n- healthMonitorCommon.calculateSeverity\n- EvtMgmtEventAlertGenerato\n- openAlert\n- closeAlert\n\n\n |