Health Check

The built-in health check reports the status of DAP Servers (Master and Standbys).


When you are scaling and managing DAP, the health check helps you determine when DAP Servers are up and ready for traffic. The health check reports the following information about a DAP Server: 

  • Status of each service running on the DAP Server.

  • Status of the internal database on the DAP Server.

  • Status of replication.

  • Overall status of the DAP Server.

Health check using the API

You can request health checks against any cluster node using the Conjur API. These routes do not require authentication.

For more information, see Health Check.

Check follower health

Run the health route on a Follower to determine if that Follower is able to service requests. If the follower returns HTTP 200, or its status is ok in a curl response, it means that the Follower is operational.


A health check on a Follower does not reflect the status of the Master. A Follower's status can be ok, meaning that it is available to service requests, even when the Master is experiencing problems.

Health check in the UI

The DAP UI shows a summary of health status for the nodes in a DAP cluster. If you have a simple configuration with just one node, the UI shows the status of the single node.

In 5.2.3 and later, the UI does not show the health status of followers.

To see the health summary in the UI: 

  1. Log into the UI. See User Interface.

  2. Click the Tools icon in the top right corner.

  3. Select Conjur Cluster.

    The window lists nodes and health for each one in the following categories: Services, Database, Replication Status, and Free Space. The Good status indicates healthy.