How to Configure and Test Alerting in Neverfail Heartbeat v5.3 through v6.0



This Knowledgebase article provides information about how to configure alerts and set reporting levels using the Neverfail Heartbeat Management Client.

More Information

The Neverfail Heartbeat Management Client allows you to configure alerts and customize the actions taken by Neverfail when the alert is triggered.


How to Configure Alerts

  1. Configure alerts by first navigating to the screen on the Neverfail Heartbeat Management Client.  Do this by selecting the Alerts -> Configuration tab.
  2. Critical red alerts and less serious yellow alerts can be manually reconfigured.  The alerts are preconfigured with the recommended alerting levels.  Reconfigure alerts to yellow or red by selecting the Trigger Yellow Alert or Trigger Red Alert check boxes
  3. Once you are finished click the Apply button once you are finished to save your new configuration.
  4. The Reset button resets the screen to the last changes applied.

Alerts Configuration

How to Set Alerts Reporting

  1. Once you are satisfied with the trigger levels, select the Reporting tab to configure the recipients of emailed alerts. Emails can be sent for both red and yellow alert triggers.
  2. In order to configure alerts, the check boxes 'Send mail on red alert' and/or 'Send mail on yellow alert' must be selected.
  3. Enter the recipients fully qualified email addresses into rows in the table 'Mail Recipients' for the trigger level alert.
  • Add a row by clicking the Add Row button.
  • Delete an email address from the tables by clicking the Delete Row button.
  • Clear an entire recipient list table by clicking the Trash Can button.

Alerts Reporting

The ‘Subject’ and ‘Content’ text fields offer a template for email messages that will be sent to recipients. They can be customized and allow the use of Neverfail specific informational variables as detailed below:

Variable Value
$EventId Id of trigger event
$EventName Name of event
$EventDetail Detail message for event
$EventHostName The name of the host where the event took place
$EventHostRole The role (active/passive) of the server where the event took place
$EventHostId The identity(Primary/Secondary)of the server where the event took place
$EventTime The time at which event occurred

Although you can configure alerts to suit your requirements, Neverfail recommends that the preconfigured content remains the same and any adjustments are made in addition.

An alternative method of issuing e-mail alerts is to run a command, by selecting the Run Command check box. A Run Command can be either a script or a command line argument to run on the alert trigger.

Alert Test

Once the alert recipients and or actions to be run have been defined, the Apply button must be selected to save the changes and apply the notification rules defined.

The Reset button resets the screen to the last changes applied.

How to Test Alerts

Alert reporting may be tested without the need to trigger an alert (and therefore jeopardize the operation of the active Server), by clicking the Test Alert Reporting button.

  1. Configure the mail host, send mail address and authentication configuration via Neverfail Heartbeat Management Client System -> Configuration. Once complete, click on Apply .
  2. Go to the Alerts -> Configuration tab and check that the 'Testing Alert Reporting' boxes are selected.
  3. Via the Alerts -> Reporting tab press the Test Alert Reporting .
  4. Check the mail accounts for appropriate messages.


A mis-configured or unreachable mail system will prevent email alerts from being sent and a warning event will be generated in the Management Client Log Panel as shown below:

Importance : Warning
Type : Sending mail failed
Source : Primary (while active)

Unable to mail alert message Could not connect to SMTP host:, port: 25;
nested exception is: No route to host: connect

Alerts and Escalations in versions v6.[n]

In V6.[n], alerts are still sent from the server on which they originated. The most critical case is presumably a pending failover, so there’s not much chance of passing the alert to the active server in order to have it sent, as the passive server cannot communicate to the active. The mechanism is still to configure a management IP address which allows the passive to see the mail server.

Escalations are a mechanism for handling error conditions, such as problems with replication which require restarting replication and therefore a Full System Check.They can get passed from server to server, but this is because of the internal mechanism for controlling Heartbeat groups, where one server is designated as the leader. This is not (necessarily) the active server, but the lowest numbered server in the Heartbeat cluster partition, as there is no ambiguity in this choice. Typically, this will be the primary, and typically the primary will be active, so the administrator may see the effect of, e.g. a replication restart because of a problem between secondary and tertiary being alerted by the primary.

Applies To

Neverfail Heartbeat v5.3 - v6.0

Related Information

Knowledgebase article #2039 : How to Configure Alerts and Set Reporting Levels Using the Neverfail Heartbeat Management Client in Neverfail Hearbeat v6.2 and Later


0 out of 0 found this helpful



Please sign in to leave a comment.