-
Notifications
You must be signed in to change notification settings - Fork 615
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Extra Prometheus metrics #309
Comments
Also the metrics endpoint is not secured with a password if I just add the SPI. The metrics endpoint is just reachable at Any Idea how to fix this? Is there any way to change the port for the SPI? |
There is no solution from the developers - but it should be trivial to configure nginx to block it, or to add authentication. |
You can add an init container or use a custom image. Adding an option to support multiple scrape endpoints is certainly something I can look into. |
I'll gladly add it as an init container - thats what I did before. But having to manage an extra servicemonitor, along with the helm chart, is cumbersome. :) |
Yes I did that and also needed to lock the endpoint for the metrics. Here is my NGINX Ingress Config to block requests to /auth/realms/master/metrics. I did not test if there will be an endpoint for every realm, but for now it was working.
|
It does indeed look like it would suit my needs! Thanks a lot! :) |
@Tim-Schwalbe Would you mind sharing your init container config? |
@harshitmahapatra Here it is:
and here is the ingress with the regEx:
|
@Tim-Schwalbe Thank you very much 😃! |
For the Keycloak 11 rewrite of the chart, it seems that the supported metrics were changed away from the Keycloak Metrics SPI[1], to use the internal Wildfly Prometheus metrics[2]. They provide quite different metrics, as far as I can see. The SPI exposes keycloak events, such as signup and logins.
If I wanted to add the SPI, I could just add it as an init container. But, I would need to add an additional ServiceMonitor manually, since the chart does not support the additional configuration.
How about the chart support the SPI, or at least multiple scrape endpoints?
[1] https://github.com/aerogear/keycloak-metrics-spi
[2] https://docs.wildfly.org/16/Admin_Guide.html#exposed-metrics
The text was updated successfully, but these errors were encountered: