Dev Tools · 20h ago
Instrumenting Keycloak SPI to catch silent JDBC bugs without code review
A developer found a Keycloak SPI provider making duplicate JDBC calls per user lookup, doubling database load silently. To catch such issues automatically, they added Sentry tracing to log each query as a child span and capture SQL exceptions. The fix prevents future performance bugs from going unnoticed until a code review.
Meridian48 take
This is a practical example of observability in custom enterprise software, but the approach is niche and unlikely to impact most developers.
Read the full reporting
Instrumenting a Keycloak SPI provider so the next silent JDBC bug doesn't need a code review to find it →
DEV Community
keycloakobservability