Repository navigation
Keycloak Operator 26.1.0 #36650
|
Hello everyone, I have deployed Keycloak via Keycloak Operator v26.1.0. I have a couple of questions:
Regards, |
Replies: 2 comments 1 reply
The default smallry health endpoints are active - if you look at the operator deployment you will see the probes. The smallrye metrics extension is not included, so nothing else is available at the JVM / application level. There should still be some default pod metrics available as well.
Quarkus json logging requires adding the json logging extension - https://quarkus.io/guides/logging#json-logging - it would take an enhancement request to add that into the operator and disable it by default. Alternatively you can build the operator image from source and include that extension in the operator pom. cc @mabartos - could be good to add to your extension project notes / directions for the operator as well. |
|
With respect to pod metrics, I suppose you are referring to kubelet
(cadvisor) metrics. I believe it would be great to have some SLIs to
determine if the operator is working successfully.
I’m currently at day 1 with plans to possibly acquire a license for the RH
Build of Keycloak. Do you know if these changes are allowed under support?
Thank you for you help Steven.
…On Tue, Jan 21, 2025 at 16:47 Steven Hawkins ***@***.***> wrote:
Is it possible to gather metrics about the operator, such as JVM health?
The default smallry health endpoints are active - if you look at the
operator deployment you will see the probes. The smallrye metrics extension
is not included, so nothing else is available at the JVM / application
level. There should still be some default pod metrics available as well.
I attempted to configure the Keycloak Operator with
QUARKUS_LOG_CONSOLE_JSON=true to enable structured JSON logs, but I
couldn’t get it to work. How can I configure the JSON format for the logger
?
Quarkus json logging requires adding the json logging extension -
https://quarkus.io/guides/logging#json-logging - it would take an
enhancement request to add that into the operator and disable it by
default. Alternatively you can build the operator image from source and
include that extension in the operator pom.
cc @mabartos <https://github.com/mabartos> - could be good to add to your
extension project notes / directions for the operator as well.
—
Reply to this email directly, view it on GitHub
<#36650 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACG2FUA4AMZ5PHK3A4KB7IT2LZT2PAVCNFSM6AAAAABVSWXA2KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJQGQZDKNY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The default smallry health endpoints are active - if you look at the operator deployment you will see the probes. The smallrye metrics extension is not included, so nothing else is available at the JVM / application level. There should still be some default pod metrics available as well.
Quarkus json logging requires adding the json logging extension - https://quarkus.io/guides/logging#json-logging - it would take an e…