Skip to content
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

[bitnami/keycloak] Issue with metrics into ServiceMonitor #30370

Closed

Conversation

RDemarneffe
Copy link

Description of the change

Allow using different ports into ServiceMonitor for instance metrics and master realm metrics.

Benefits

Correctly configure prometheus for grabbing metrics.

Possible drawbacks

None.

Applicable issues

Checklist

  • Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
  • Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
  • Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
  • All commits signed off and in agreement of Developer Certificate of Origin (DCO)

…and master realm metrics.

Signed-off-by: Renaud Demarneffe <[email protected]>
Signed-off-by: Renaud Demarneffe <[email protected]>
@@ -1011,7 +1011,8 @@ metrics:
## @param metrics.service.ports.http Metrics service HTTP port
##
ports:
http: 9000
metrics: 9000
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution. Please note you need to add the metadata for this new parameter, see the above metadata corresponding to the already existing parameters.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated the metadata.

RDemarneffe and others added 3 commits November 9, 2024 19:51
@carrodher carrodher added verify Execute verification workflow for these changes in-progress labels Nov 10, 2024
@github-actions github-actions bot removed the triage Triage is needed label Nov 10, 2024
@github-actions github-actions bot assigned fmulero and unassigned carrodher Nov 10, 2024
Signed-off-by: Bitnami Containers <[email protected]>
Copy link
Collaborator

@fmulero fmulero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot @RDemarneffe, in #30095 didn't see that instance and realm metrics were using different interfaces. Great work!

I was revisiting monitoring features and WDYT about this:

## @param metrics.service.annotations [object] Annotations for enabling prometheus to access the metrics endpoints
##
annotations:
prometheus.io/scrape: "true"
prometheus.io/port: "{{ .Values.metrics.service.ports.http }}"

I think is worth to change it with something like this:

    ## @param metrics.service.annotations [object] Annotations for enabling prometheus to access the metrics endpoints
    ##
    annotations:
      prometheus.io/scrape: "true"
      prometheus.io/port: "{{ .Values.metrics.service.ports.metrics }}"
      prometheus.io/path: "{{ (.Values.metrics.serviceMonitor.endpoints | first).path }}"

@erwanval
Copy link
Contributor

@RDemarneffe This has been fixed by #30303, merged yesterday

@fmulero
Copy link
Collaborator

fmulero commented Nov 13, 2024

Thanks @RDemarneffe. I'll close this PR.

@fmulero fmulero closed this Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keycloak solved verify Execute verification workflow for these changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[bitnami/keycloak] Issue with metrics into ServiceMonitor
5 participants