Update health.adoc to link to the Quarkus SmallRye Health docs (#22324)
This commit is contained in:
parent
062c0f75f8
commit
b776746455
1 changed files with 23 additions and 4 deletions
|
@ -10,15 +10,20 @@ includedOptions="health-enabled">
|
|||
|
||||
Keycloak has built in support for health checks. This {section} describes how to enable and use the Keycloak health checks.
|
||||
|
||||
== Keycloak Health checks
|
||||
== Keycloak health check endpoints
|
||||
|
||||
Keycloak exposed health endpoints are three:
|
||||
Keycloak exposes 4 health endpoints:
|
||||
|
||||
* `/health`
|
||||
* `/health/live`
|
||||
* `/health/ready`
|
||||
* `/health/started`
|
||||
* `/health`
|
||||
|
||||
The result is returned in json format and it looks as follows:
|
||||
See the https://quarkus.io/guides/smallrye-health#running-the-health-check[Quarkus SmallRye Health docs] for information on the meaning of each endpoint.
|
||||
|
||||
These endpoints respond with HTTP status `200 OK` on success or `503 Service Unavailable` on failure, and a JSON object like the following:
|
||||
|
||||
.Successful response for endpoints without additional per-check information:
|
||||
[source, json]
|
||||
----
|
||||
{
|
||||
|
@ -27,6 +32,20 @@ The result is returned in json format and it looks as follows:
|
|||
}
|
||||
----
|
||||
|
||||
.Successful response for endpoints with information on the database connection:
|
||||
[source, json]
|
||||
----
|
||||
{
|
||||
"status": "UP",
|
||||
"checks": [
|
||||
{
|
||||
"name": "Keycloak database connections health check",
|
||||
"status": "UP"
|
||||
}
|
||||
]
|
||||
}
|
||||
----
|
||||
|
||||
== Enabling the health checks
|
||||
It is possible to enable the health checks using the build time option `health-enabled`:
|
||||
|
||||
|
|
Loading…
Reference in a new issue