Dima Zyuryaev
Dima Zyuryaev
> Hi, > We are using the daemonset to send logs to centralized Graylog server using the following image: fluent/fluentd-kubernetes-daemonset:v1.2-debian-graylog. > > The logs are sent to Graylog and we...
I am not sure this project is active, otherwise i would suggest a pull request. debian-buster is no longer in ftp.debian.org, but in the debian archive, this is why you...
The following template (custom) has been tested in our Keycloak K8S Kubernetes clusters and found working, all metrics `https` and `http` endpoints appear in Grafana. servicemonitorcustom.yaml ```yaml {{- /* This...
This is primarily about adding the `scheme` attribute to the `ServiceMonitor` object, as the tls configuration for the scraper application should be managed separately, not related to this chart
Can confirm that in latest 26.0.7 this issue has been resolved
Did not work for me. I can access kc internal service on port 9000, but while trying to see `/metrics` endpoint get an empty reply from the server. `curl --head...
I have noticed that metrics from realms are accesible via old 8080 http port, and i did not enabled old-mode compatibilty mode via ENV ``` curl -sSf http://idp-keycloak-metrics:8080/realms/master/metrics | head...
It is a `bitnami` [container](https://github.com/bitnami/containers/tree/main/bitnami/keycloak), version [25.0.4](https://hub.docker.com/layers/bitnami/keycloak/25.0.4-debian-12-r0/images/sha256-13976ea12c6af15a5a755be4e1c1350e71eacdca31ebfe8026fab0355ee5614f?context=explore) ``` {"timestamp":"2024-08-21T19:24:24.819308896Z","sequence":9299,"loggerClassName":"org.jboss.logging.Logger","loggerName":"io.quarkus","level":"INFO","message":"Keycloak 25.0.4 on JVM (powered by Quarkus 3.8.5) started in 20.291s. Listening on: http://0.0.0.0:8080 and https://0.0.0.0:8443. Management interface listening on https://0.0.0.0:9000.","threadName":"main","threadId":1,"mdc":{},"ndc":"","hostName":"idp-keycloak-0","processName":"QuarkusEntryPoint","processId":1} ```...
Finally, everything is functioning with the following configuration, though in a somewhat unexpected way. The issue I previously encountered was due to the fact that my main Keycloak server runs...