Heartbeat is a mechanism that notifies a client about any change in policies and configurations. The client sends the heartbeat to the CipherTrust Manager indicating that it is alive. In response, the CipherTrust Manager notifies client about any changes in the configurations and policies.
Heartbeat configuration parameters
|Heartbeat Interval||Time interval after which a client needs to send heartbeat notification to the CipherTrust Manager to get updated policies and configurations. The default value is 300s.|
|Heartbeat Timeout Count||Number of missed heartbeats after which a client marks a CipherTrust Manager instance inactive.|
|Heartbeat Threshold||Number of missed heartbeats after which the CipherTrust Manager changes client's state to error.|
These parameters are configured while defining an Application. Refer to Managing Applications for details.
If the CipherTrust Manager is not able to receive heartbeat from a client until
heartbeat_interval, the client's state is changed from healthy to warning. If the CipherTrust Manager does not receive heartbeat notification until
heartbeat_threshold, the client's state is changed from warning to error.
If a client is not able to send heartbeat notification to the CipherTrust Manager until the
heartbeat_timeout_count, the client marks the CipherTrust Manager as inactive. For example, if
Heartbeat Interval is 30 seconds and
Heartbeat Timeout Count is 5, and the client is not able to send the heartbeat notification till 150 seconds, the client marks the CipherTrust Manager instance as inactive.