Heartbeat parameters
Heartbeat parameters
Parameter | Description | Type |
|---|---|---|
HeartbeatEnabled | Indicates whether the heartbeat monitoring mechanism is enabled or not. | Boolean |
HeartbeatInterval | Default interval between two beats, if not specified in the data object. | Number |
HeartbeatMissedCritical | Default number of consecutive missed beats that are needed to generate a critical event, if not specified in the data object. | Number |
HeartbeatMissedMinor | Default number of consecutive missed beats that are needed to generate a minor event, if not specified in the data object. | Number |
HeartbeatMissedWarning | Default number of consecutive missed beats that are needed to generate a warning event, if not specified in the data object. | Number |
The heartbeat feature enables a specific cell, called the monitoring cell, to monitor one or more cells, called the monitored cell or cells, for enabled access by the monitoring cell.
The parameter in the mcell.conf file of the monitored cell should be HeartbeatEnabled=Yes. By default, the monitored cell sends a beat every 300 seconds.
Heartbeats are configured through MC_CELL_HEARTBEAT dynamic data objects in the monitoring cell. An MC_CELL_HEARTBEAT dynamic data object contains information, such as the name of the cell to be monitored, the length of the expected time intervals between the heartbeats, and the number of heartbeats that must be missed to generate corresponding internal events in the monitoring cell.
The cell receives the dynamic data object either by loading it from the data directory, receiving it through an mposter call, or viewing it in the Administrative view of the administration console. The monitoring cell sends a request to the monitored cell. The monitored cell sends a heartbeat back to the monitoring cell at the specified intervals. If the monitoring cell does not receive a heartbeat in the expected timeframe, the monitoring cell generates an alert that can be viewed in the operator console console.
The default settings for missing heartbeats are as follows:
- 1 missed heartbeat generate a warning event
- 2 missed heartbeats generate a minor event
- 3 missed heartbeats generate a critical event
For example, cell 1 is the monitoring cell, which sends a request to cell 2, the monitored cell. If it does not receive a response at a specified interval, then the monitoring cell sends an alert that can be seen in the operator console.
After a monitoring cell terminates and restarts, it is aware of prior requests for heartbeats because it rereads the dynamic data objects that are stored in the cell repository mcdb. After it rereads the data, the monitoring cell attempts to resend the request to the monitored cell.
If the monitored cell terminates, the monitoring cell resends the request for heartbeats at the specified intervals. The following table lists the MC_CELL_HEARTBEAT slots.
Heartbeat slots
Slot | Description |
|---|---|
cell | The name of the target monitored cell. |
enable | Indicates whether the heartbeat is enabled or disabled, using the following values: |
last_time | The time that the last heartbeat was received. |
interval | Specifies the length of the time interval between heartbeats. |
missed_warning | Specifies the number of missed heartbeats before a WARNING event is generated. |
missed_minor | Specifies the number of missed heartbeats before a MINOR event is generated. |
missed_critical | Specifies the number of missed heartbeats before a CRITICAL event is generated. |
missed | The number of consecutive missed heartbeats. |