# Observability in Keycloak 26.2

DevFeed: [Observability in Keycloak 26.2](<https://devfeed.tech/articles/observability-in-keycloak-26-2-31702.md>)

Original publisher: [Read original article](<https://www.keycloak.org/2025/04/observability-26-2>)

Author: Michal Hajas

Published: 2025-04-24T00:00:00Z

Content type: release

Language: en

Sources: [Keycloak Blog](<https://devfeed.tech/sources/keycloak-blog.md>)

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [tracing](<https://devfeed.tech/topics/tracing.md>)

Tags: [availability](<https://devfeed.tech/tags/availability.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [guide](<https://devfeed.tech/tags/guide.md>), [idm](<https://devfeed.tech/tags/idm.md>), [kerberos](<https://devfeed.tech/tags/kerberos.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sso](<https://devfeed.tech/tags/sso.md>), [traces](<https://devfeed.tech/tags/traces.md>), [tracing](<https://devfeed.tech/tags/tracing.md>)

## AI overview

This article describes observability improvements in Keycloak 26.2. It explains how service level indicators and metrics can detect performance degradation, how selected metrics help identify causes, and how Prometheus and Grafana dashboards support troubleshooting. It also introduces tracing for examining the steps and timing of specific requests.

## Source excerpt

When running a central single sign on service like Keycloak in production, you need to understand how well the system performs and whether there are service degradations. Having a proper monitoring stack in place is essential for this. Moreover, when the system performance degrades, it is crucial to identify which part of the system is causing the problem to address it. In the latest Keycloak release, all the above became more straightforward and works without additional extensions. Read on to learn more and watch the recording of our meetup on May 7th! Hey Keycloak! How are you? Users rely on Keycloak to log in to their applications, and service level indicators (SLIs) capture the key metrics capturing that behavior. Misbehavior of the system can be detected by monitoring these SLIs. One of the indicators can be the availability of the system. The indicator for availability can be defined as: percentage of the time the system can answer requests. The lower the indicator is for your system, the less available it was in the observed period. Find an example set of SLIs for Keycloak and more details on this topic in the Monitoring performance with Service Level Indicators guide. Oh no! You are not doing well? Now we know how to detect when Keycloak is not performing well. But what should I do when a service level indicator shows a degradation of the service? This situation usually means some part of Keycloak does not perform well. However, from the indicator itself, it is hard to say what part of Keycloak it is. To identify the culprit of the problem, we provide the Troubleshooting using metrics guide that lists chosen metrics. Using these metrics, you can visualize what is happening in your deployment and down problems. Some examples of metrics from the guide are listed below: Number of operations performed by Keycloak like password hashes, login flows, token refreshes, etc. Memory usage Database connection pool utilization Number of HTTP requests per URL and outcome