Provides metrics for Keycloak user/admin events and user/client/session count. Tested on Keycloak 21-25.
aerogear/keycloak-metrics-spi is an alternative to this plugin but is not well maintained. This implementation is different:
- no Prometheus push (event listener only adds counter to Micrometer)
- no realm specific Prometheus endpoint, only
/metrics
(from Quarkus) - no jvm/http metrics, this is already included in Keycloak
- different metric names, can relace model ids with name (see configuration)
- deployed to maven central and very small (15 kb vs. 151 KB aerogear/keycloak-metrics-spi)
- gauge for active/offline sessions and user/client count
Resuses micrometer from Quarkus distribution to add metrics for Keycloak for events.
User events are added with key keycloak_event_user_total
and tags:
type
: EventType from Event#typerealm
: realm id from Event#realmIdclient
: client id from Event#clientIderror
: error from Event#error, only present for error types
Examples:
keycloak_event_user_total{client="test",realm="9039a0b5-e8c9-437a-a02e-9d91b04548a4",type="LOGIN",error="",} 2.0
keycloak_event_user_total{client="test",realm="1fdb3465-1675-49e8-88ad-292e2f42ee72",type="LOGIN",error="",} 1.0
keycloak_event_user_total{client="test",realm="1fdb3465-1675-49e8-88ad-292e2f42ee72",type="LOGIN_ERROR",error="invalid_user_credentials",} 1.0
Admin events are added with key keycloak_event_admin_total
and tags:
realm
: realm id from AdminEvent#realmIdoperation
: OperationType from AdminEvent#operationTyperesource
: ResourceType from AdminEvent#resourceTypeerror
: error from AdminEvent#error, only present for error types
Examples:
keycloak_event_admin_total{error="",operation="CREATE",realm="1fdb3465-1675-49e8-88ad-292e2f42ee72",resource="USER",} 1.0
keycloak_event_admin_total{error="",operation="CREATE",realm="9039a0b5-e8c9-437a-a02e-9d91b04548a4",resource="USER",} 1.0
Set to true
(the default value) than replace model ids from events with names:
Metrics:
keycloak_event_user_total{client="test-client",error="",realm="test-realm",type="LOGIN",} 2.0
keycloak_event_user_total{client="other-client",error="",realm="other-realm",type="LOGIN",} 1.0
keycloak_event_user_total{client="other-client",error="invalid_user_credentials",realm="other-realm",type="LOGIN_ERROR",} 1.0
Set to true
(default is false
) to provide metrics for user/client count per realm and session count per client. Metrics:
# HELP keycloak_users
# TYPE keycloak_users gauge
keycloak_users{realm="master",} 1.0
keycloak_users{realm="my-realm",} 2.0
keycloak_users{realm="other-realm",} 1.0# HELP keycloak_active_user_sessions
# TYPE keycloak_active_user_sessions gauge
keycloak_active_user_sessions{client="admin-cli",realm="userCount_1",} 0.0
keycloak_active_user_sessions{client="admin-cli",realm="userCount_2",} 0.0
keycloak_active_user_sessions{client="admin-cli",realm="master",} 1.0
# TYPE keycloak_active_client_sessions gauge
keycloak_active_client_sessions{client="admin-cli",realm="userCount_1",} 0.0
keycloak_active_client_sessions{client="admin-cli",realm="userCount_2",} 0.0
keycloak_active_client_sessions{client="admin-cli",realm="master",} 0.0
# TYPE keycloak_offline_sessions gauge
keycloak_offline_sessions{client="admin-cli",realm="userCount_1",} 0.0
keycloak_offline_sessions{client="admin-cli",realm="userCount_2",} 0.0
keycloak_offline_sessions{client="admin-cli",realm="master",} 0.0
If KC_METRICS_STATS_ENABLED
is true
this will define the interval for scraping. If not configured PT60s
will be used.
If KC_METRICS_STATS_ENABLED
is true
this envs will define logging if scraping takes to long. Both envs are parsed as java.lang.Duration
.
Default values:
KC_METRICS_STATS_INFO_THRESHOLD
: 50% ofKC_METRICS_STATS_INTERVAL
= 30sKC_METRICS_STATS_WARN_THRESHOLD
: 75% ofKC_METRICS_STATS_INTERVAL
= 45s
If scrapping takes less than KC_METRICS_STATS_INFO_THRESHOLD
duration will be logged on debug level.
Can be found here: kokuwaio/keycloak keycloak-metrics.json
For usage in Testcontainers see KeycloakExtension.java
Registries:
This images are based on busybox, so you can use cp to copy the jar into your keycloak.
Check: kokuwaio/keycloak
Dockerfile:
###
### download keycloak event metrics
###
FROM debian:stable-slim AS metrics
RUN apt-get -qq update
RUN apt-get -qq install --yes --no-install-recommends ca-certificates wget
ARG METRICS_VERSION=1.0.0
ARG METRICS_FILE=keycloak-event-metrics-${METRICS_VERSION}.jar
ARG METRICS_URL=https://repo1.maven.org/maven2/io/kokuwa/keycloak/keycloak-event-metrics/${METRICS_VERSION}
RUN wget --quiet --no-hsts ${METRICS_URL}/${METRICS_FILE}
RUN wget --quiet --no-hsts ${METRICS_URL}/${METRICS_FILE}.sha1
RUN echo "$(cat ${METRICS_FILE}.sha1) ${METRICS_FILE}" sha1sum --quiet --check --strict -
RUN mkdir -p /opt/keycloak/providers
RUN mv ${METRICS_FILE} /opt/keycloak/providers
###
### build keycloak with metrics
###
FROM quay.io/keycloak/keycloak:25.0.1
ENV KEYCLOAK_ADMIN=admin
ENV KEYCLOAK_ADMIN_PASSWORD=password
ENV KC_HEALTH_ENABLED=true
ENV KC_METRICS_ENABLED=true
COPY --from=metrics /opt/keycloak/providers /opt/keycloak/providers
RUN /opt/keycloak/bin/kc.sh build
Run:
docker build . --tag keycloak:metrics
docker run --rm -p8080 keycloak:metrics start-dev