Version

Argent Advanced Technology 3.1A-1610-C to 5.1A-1704-B

Date

Monday, 26 June 2017

Summary

Customer relying on internal heartbeat on 5.1A-1704-B (or earlier) AND is on Non-Stop Motor architect may notice single heartbeat is sent from any Motor instead of each Motor.

Heartbeat delivers extra visibility on alive status of Argent. It is interval controlled.

Before 3.1A-1610-C, customers may create heartbeat at Relator level. This approach causes unwanted events on Argent Console.

From Argent Advanced Technology 3.1A-1610-C, internal heartbeat at Supervising Engine level is available. (see https://help.argent.com/#KBI_311496)

Once internal heartbeat is configured, we expect one notification for EACH Supervising Engine.

A Supervising Engine is found in Main Engine, Motor and Daughter Engine.

Heartbeat Configuration Screen (Non-Stop Motor Environment)

Technical Background

Argent heartbeat is scheduled to run as per defined configuration under Engine Manager inside “Control Information > Administration”.

Behind the scene, it is a Relator task named $REL_HEARTBEAT. The schedule is visible in Scheduled Monitoring Tasks screen. Customer can inspect its Relator Trace Log, too.

The scheduling of Relator tasks in Non-Stop Motor is typically dynamic and is executed by a single Motor. This is a feature to prevent task duplication from monitoring perspective.

However, the same feature prevented notifications sent for each Motor. This has been changed in 1707-A and later so that there will be a heartbeat sent for EACH Motor.

Resolution

Upgrade to Argent Advanced Technology 5.1A-1707-A or later.