Sebastian Łaskawiec

> Was there any thought of bringing the concerns and problems with directly utilizing SmallRye Health back to the project itself: https://github.com/smallrye/smallrye-health? @kenfinnigan What concerns do you mean exactly? If...

> Missing a clear list of what checks we should have @stianst The list has been provided in lines 30-32. We currently have only 3 of them: ``` * `db`...

Dear all, I've just uploaded the third iteration of the Healthcheck proposal. Differences from the previous version: - I removed both External IdPs and User Federation bits from the scope...

Today morning, both @stianst and I had a discussion on the future plans of both Healthcheck API and the Observability designs. We agreed that our main focus will be Quarkus-based...

Dear all, After some discussion with Stian, I've created another iteration of the proposal. You may find it here: https://github.com/keycloak/keycloak-community/pull/55 Differences from the previous version: - The design focuses on...

I've just pushed a minor review to address @hmlnarik 's comment. After the implementation, I'll review this again and make sure all the bits match. After this step - it...

@miquelsi @vmuzikar @ASzc @abstractj The last bits have just been added. @abstractj Could you please merge it?

> This is a great start, but there's still quite a bit that needs to be done before we can agree on what exactly it should look like. One very...

Dear all, I've just uploaded the second iteration of the Observability proposal. Differences from the previous version: * Proposed the new split for Keycloak Services: Admin, Account, OIDC, SAML, Token...

> would be possible to add how we plan to protect those endpoints? I can think about mTLS, but it would be nice to make it clear into the document....