DumbMonit
用 DumbMonit 监控 Keycloak
测试版Readiness and database health, version, realms (disabled ones), active sessions and users per realm.
产品说明为英文，与产品内一致。页面标签使用您的语言。
DumbMonit 监控的内容
Whether Keycloak can really log people in: readiness with the database check, version, realms (a disabled one is a locked-out population), and, with a service account, active sessions and users per realm.
典型用途. Identity: readiness and database, realms, sessions, users
示例
- Keycloak 25 and later
- Keycloak 24 and earlier
连接方式
您需要准备
- Client ID / secretA service-account client with read-only roles. DumbMonit asks for a token at each probe.
无需账户。
需要开放的网络端口
8080/TCPAPI (HTTP, default)9000/TCPHealth checks on the management port (Keycloak 25 and later)443/TCPOnly with the https scheme behind a reverse proxy
设置步骤: Let DumbMonit read Keycloak's health and realms
Run Keycloak with health checks on, with the option below. From Keycloak 25 they answer on the management port 9000.
KC_HEALTH_ENABLED=trueOptional, for realms, sessions and users: in the master realm, create a client named as follows, with Client authentication and Service accounts roles on, and Standard flow off.
dumbmonitOn that client's Service accounts roles tab, assign the client roles listed below, then copy the secret from its Credentials tab.
In DumbMonit, enter Keycloak's address and the client ID and secret, or choose None (health checks only).
注意. Keycloak 24 and earlier serve the health checks on the main port: set the health port option to same. Health checks must be enabled on the server, or DumbMonit reports a missing /health/ready.