Heartbeat Configuration

Heartbeat is a periodic mechanism to notify the CipherTrust Manager that a client is alive. It means, the client is available to receive any updates (changes in the configurations and policies) from the CipherTrust Manager.

Heartbeat Configuration Parameters

These parameters are configured while defining an Application. Refer to Defining applications for details.

• If the CipherTrust Manager doesn't receive the heartbeat from a client after Heartbeat Interval, the client's state on the CipherTrust Manager changes from healthy to warning. However, if the CipherTrust Manager doesn't receive the heartbeat in continuous Heartbeat Threshold attempts, the client's state changes from warning to error.

• If a client can't receive any response from the CipherTrust Manager in continuous Heartbeat Timeout Count attempts, the client marks itself as unhealthy. For example, if Heartbeat Interval is 30 seconds and Heartbeat Timeout Count is 5, and the client doesn't receive any response from the CipherTrust Manager within 150 seconds (that is, within a total of 5 continuous attempts, each every 30 seconds), the client marks itself as unhealthy. The client will continue to perform protect and reveal operations using the current configuration until the time specified in Key Cache Expiry is reached.