Allow to customize the metrics port of the ServiceMonitor #228
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #221
Description of the change
Allow to customize the metrics port of the ServiceMonitor, i.e. when using OpenTelemetry.
Existing or Associated Issue(s)
Additional Information
Currently, the metrics port in the ServiceMonitor is set to the http-backend port. When using OpenTelemetry as recommended with Prometheus exporter, this port needs to be different.
OpenTelemetry's default port for Prometheus exporter is 9464, but it can be customized.
So the chart should allow setting a custom port for the ServiceMonitor. The default value remains
http-backend
.Checklist
Chart.yaml
according to semver.values.yaml
and added to the README.md. The helm-docs utility can be used to generate the necessary content. Usehelm-docs --dry-run
to preview the content.ct lint
command.