Active Monitoring Module
The Active Monitoring Module helps you make sure that errors are acknowledged and fixed by IT staff, or escalated they are not addressed quickly.
Alerting revolves around the Operator Message system. When an alert is raised, an Operator Message is created. This Operator Message must be replied to in order to acknowledge the alert.
Alerts themselves are children of Operator Messages, and can be monitored via the Operator Message monitor. An Operator Message that has alerts attached to it will have a [+] next to it in the monitor.
There are two ways operators and managers can be informed of errors:
- Operator Messages
- Email or SMS
The key features of the Active Monitoring module are:
- Operator Message integration: All alerts are raised as Operator Messages and are visible in the Operator Message console.
- Acknowledgment: An alert must be acknowledged by replying to its Operator Message in order to be cleared.
- Alert escalations: Unacknowledged alerts can be escalated to email or SMS through shared escalation pathways.
- Rule-based configuration: Alerts can be defined as rules that are separate from the objects that cause them to be raised.
Alerts can be defined for the following objects:
- Process Servers: Any status change. Rules are defined based on a Process Server name pattern.
- Processes: Any status change. Rules are defined based on a Process Definition name pattern and the parameters.
- Monitors: Any change in severity. Rules are defined based on a monitor.
Note: The Active Monitoring Module requires the Module.Alerting license key.
The alerting system consists of three types of object:
- Alert Sources: Object-specific rules that are defined for when alerts should be created, see below.
- Process Server Alert Sources: Used when a Process Server loses the connection to a remote system.
- Process Alert Sources: Used when processes, Steps, or Chains reach an undesired status.
- Ad Hoc Alert Sources: Used in chains to fire alerts with the System_Alert_Send Process Definition.
- Monitor Alert Sources: Used when a monitor reaches a certain severity.
- Alert Escalations: A set of rules stating who to send an alert to, how long to wait for acknowledgment, and which alert to escalate to if the alert is unacknowledged.
- Alert Gateways: A set of rules determining how messages are formatted and sent.
An alert is raised by an alert source, creating an Operator Message that needs to be responded to. The alert source specifies the first alert escalation to use. From then on the alerting escalation system decides how long to wait for acknowledgment, and what the next alert is. While the alert is being escalated, messages are sent via the alert gateways to elicit a response. As soon as the Operator Message is replied to, the alert is acknowledged and no further automatic action is taken.
Alerting CAR File
An alerting CAR file is available in Configuration > Software under Download CAR Files. It contains these Active Monitoring Module objects.
GLOBAL.DelayedProcesses: Process Definition alert source that fires for delayed processes.GLOBAL.ErroneousProcesses: Process Definition alert source that fires for processes that have reached status Error, Killed, or Unknown.GLOBAL.NotConnectedProcessServers: Process Server alert source that fires for Process Servers that have reached status Connecting, PartiallyRunning, or Shutdown for more than 2 minutes.