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
| Parameters | Description |
|---|---|
| Heartbeat Interval | Time interval after which a client needs to send a heartbeat to the CipherTrust Manager to get updated policies and configurations. The default value is 300s. |
| Heartbeat Timeout Count | Number of continuously missed heartbeats after which a client marks itself as unhealthy. After this count, the CipherTrust Manager revokes the client and the client stops performing any cryptographic operations. Possible values: — -1: client will continue to send the heartbeats until it is alive and the CipherTrust Manager will not revoke the client. — any positive integer |
Tip
The CipherTrust Manager updates status of all the clients after every 5 minutes based on the number of missed heartbeats.
These parameters are configured while defining an Application.
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 continuousHeartbeat Thresholdattempts, 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 Countattempts, the client marks itself as unhealthy. For example, ifHeartbeat Intervalis 30 seconds andHeartbeat Timeout Countis 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.
