Heartbeats failed since success

XML identifiers: hrtbt_fail_snc_succ and #var:HBFailSinceSucc#, per default placed within the value strings of HBL16 (key) and HBV16 (value replacement), respectively. Can be removed by redefining this key/value pair, and may be moved to any of the other HBL/HBV01-25 pairs (see example).

Purpose: The successful heartbeat count (since last failed heartbeat transfer) counts the number of actual heartbeats that has failed transfer to logging server since the last successful heartbeat transfer occured. This value can be viewed by users (and local admins) via the device settings login popup (see illustration). The failed heartbeat count since last failure (shown as Failed since success: 0 in illustration below) can be used for statistics, and for debugging on suspicion of faults either on app, on iPad, network or logging server. Note: This value is obviously transferred to logging server, once this number an be transferred successfully.

Revamped device settings & device information popup, adding last config read time, device IP addresses (IPv4 and IPv6), and a heartbeat success and failure summary.

Status: Currently in use.

Category: Heartbeat keys (labels and value).

Usage: Activated per default, using key/value pair HBL16 for label string, and HVL16for replacement parameter string as defined in apps internal default stup. HBL16/HVL16 can be overridden, for other purposes. Label string and replacement parameters string can (optionally) be moved to another label/value-pair (HBL/HBV01-25). See usage example, and heartbeat capture example (below).

Default:

Defaults to the pair of HBK16 with the label string hrtbt_fail_snc_succ, and a replacement parameter string HBV16 of #var:HBFailSinceSucc#. The replacement parameter string #var:HBFailSinceSucc# is replaced in app with the actual number of failures since success. The maximum size of hrtbt_succ_snc_fail count before resetting this to 0 is 2.147.483.647. This will sufficient for roughly 245.000 years of use, assuming that all heartbeat transfers (with default frequency of one each 5 minutes) will fail, before eventually being transferred.

Development status: Released in 1.1.0. Standard feature, as defined in app config.

Example: Choosing to use the WAL HeartBeat ConFiguration Key 10, and Value 10 to give heartbeats informing about the number of failed heartbeat transfers to server since last successful transfer:

<key>HBL10</key>

<string>hrtbt_fail_snc_suc</string>

<key>HBV10</key>

<string>#var:HBFailSinceSuccess#</string>


Illustration: Capure of heartbeat on logging server, as illustrated with a screen capture form a server session running on the open service requestinspector.com (highly recommended, incidentally, for development and simple testing of heartbeats). In this example, the value of hrtbt_fail_snc_suc is 0.

Heartbeat data received at logging server.

Document Revision: Nov. 2024. Rev. 1.0