You can check server status using the PingDataGovernance Server Administrative Console, the status command, or the availability servlet.
Administrative Console
You can access status information in the console, in the Status tab.
For information about how to access the console, see PingDataGovernance Administrative Console.
status command
The PingDataGovernance distribution includes the bin/status command that you can use to see various information about the server, including its status and the status of its LDAP external servers.
Availability servlet
PingDataGovernance provides an HTTP servlet extension that you can use to retrieve the
server's current availability state. The servlet accepts any GET
,
POST
, or HEAD
request sent to a specified
endpoint and returns a minimal response whose HTTP status code can help you
determine whether the server considers itself to be
AVAILABLE,
DEGRADED, or UNAVAILABLE.
The status code for each of these states is configurable, and the response can
optionally include a JSON object with an availability-state
field
with the name of the current state.
-
/available-state
This endpoint can prove useful for load balancers that should only route requests to servers that are fully available.
The following table shows the responses for this endpoint.Response Server state 200 (OK) AVAILABLE 503 (Service Unavailable) DEGRADED or UNAVAILABLE -
/available-or-degraded-state
This endpoint can prove useful for orchestration frameworks if you want to destroy and replace any instance that is completely unavailable.
The following table shows the responses for this endpoint.Response Server state 200 (OK) AVAILABLE or DEGRADED 503 (Service Unavailable) UNAVAILABLE