Heartbeat Service
Overview
The Heartbeat Service watches a concentrator connection and raises an alarm in SBN when that connection stops responding. On a fixed timer it checks the monitored address; each time the check fails a counter goes up, and once the failures reach the configured limit the service places a heartbeat timeout signal into the alarm queue so operators see it like any other alarm. A successful check resets the counter, so a single momentary blip does not generate an alarm.
Because the alarm has to be delivered even when part of the system is in trouble, the service can be pointed at more than one SBN data server. A primary connection is required; optional secondary and tertiary connections let the alarm be written to additional servers as well. The service requires a working SBN data-server connection at start-up, plus the identity of the concentrator and zone being supervised and the account the resulting alarm should be reported against.
Dashboard
Installing and managing this service is done from the SBN Services Dashboard — see <a href="/help/SBN-Services/Dashboard">here</a>.
Service Properties
Only properties specific to this service are listed here. Common service properties (SBN Server connection, Logging, SMTP) are found <a href="/help/SBN-Services/Common-Properties">here</a>.
Timer (In Seconds)
How often the service performs a check against the monitored connection.
Conc Id
Identifies which concentrator this service is supervising. The alarm the service raises is reported against this concentrator.
Zone
The zone reported with the heartbeat alarm, so operators can tell which part of the system the failure came from.
Consecutive Fails
How many checks must fail in a row before an alarm is raised. The counter resets as soon as a check succeeds, which prevents an alarm on a brief interruption.
REST URL
The address the service checks each pass to confirm the connection is alive.
SBN Error Account (CID)
The account the heartbeat alarm is placed against, so the alarm appears on the correct installation in monitoring.
SBN Server — Primary, Secondary and Tertiary
The service can be given up to three SBN data-server connections. The primary is required; the secondary and tertiary are optional and let the alarm be recorded on additional servers. The connection fields themselves are the standard ones described in <a href="/help/SBN-Services/Common-Properties">Common Properties</a>.