XML identifiers: Defines the number of heartbeats that (as seen from the viewpoint of the app) have been successfully logged on server (as signaled by server as code 200) since the last failure, or start of app. Is active per default, using HBL15 as tag (key) and HBV15 (value replacement). 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 transferred to logging server since the last heartbeat transfer failure occurd. This value can also be seen by users (and local admins) via the device settings login popup (see illustration). The successful heartbeat count since last failure (shown as Success since failed: 199 in illustration below) can be used for statistics, and for debugging on suspicion of faults either on app, on iPad, network or logging server.
Status: Currently in use.
Category: Heartbeat keys (labels and value).
Usage: Activated per default, using key/value pair HBL15 for label string, and HVL15for replacement parameter string as defined in apps internal default stup. HBL15/HVL15 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 HBK15 with the label string hrtbt_succ_snc_fail, and a replacement parameter string HBV15 of #var:HBSuccSinceFail#. The replacement parameter string #var:HBSuccSinceFail# is replaced in app with the actual number of successes. The maximum size of heartbeat count before resetting this to 0 is 2.147.483.647. This will with a heartbeat rate of one per 5 minutes (which is default from version 1.1.1 onwards) equate to roughly 245.000 years of use. Note! This does NOT restrict the total number of heartbeats that can be transferred, JUST the total number failed that is reported to the user, and to the logging server.
Development status: Released in 1.1.0. Standard feature, as defined in app config.
Example: Choosing to use the WAL HeartBeat ConFiguration Key 09, and Value 09 to give heartbeats informing about the number of successfult heartbeat transfers to server since app start:
…
<key>HBL09</key>
<string>hrtbt_succ_snc_fail</string>
…
<key>HBV09</key>
<string>#var:HBSuccSinceFails#</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_succ_snc_fail is 14.
Document Revision: Nov. 2024. Rev. 1.0