-
Notifications
You must be signed in to change notification settings - Fork 296
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
When OnCall Metrics are enabled they are exposed on path /metrics/ and not on /metrics #3597
Labels
Comments
ahladh
changed the title
When OnCall Metrics are enabled they are exposed on path /metrics/ and not on /metrics(which is a general preference when scraping metrics using prometheus)
When OnCall Metrics are enabled they are exposed on path /metrics/ and not on /metrics (which is a general preference when scraping metrics using prometheus)
Dec 24, 2023
ahladh
changed the title
When OnCall Metrics are enabled they are exposed on path /metrics/ and not on /metrics (which is a general preference when scraping metrics using prometheus)
When OnCall Metrics are enabled they are exposed on path /metrics/ and not on /metrics
Dec 24, 2023
im using chart version
and create service monitor to scrape path |
just confirmed that in chart version
metrics are exposed but only works with |
joeyorlando
added
part:metrics/logging
Relate to metric exporting or logging
and removed
part:helm/kubernetes/docker
part:alert flow & configuration
needs triage
labels
Jun 14, 2024
bck01215
added a commit
to bck01215/oncall
that referenced
this issue
Sep 25, 2024
This resolves grafana#3597
bck01215
added a commit
to bck01215/oncall
that referenced
this issue
Sep 25, 2024
This resolves grafana#3597
bck01215
added a commit
to bck01215/oncall
that referenced
this issue
Sep 25, 2024
This resolves grafana#3597
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What went wrong?
What happened:
When the Oncall plugin metrics are enabled using the variable FEATURE_PROMETHEUS_EXPORTER_ENABLED the metrics can be scraped from prometheus using the path http://<oncall-serviceip/dns>:8080**/metrics/** and not using the path http://<oncall-serviceip/dns>:8080**/metrics**
Generally when we scrape metrics using Prometheus the default path to scrape metrics is done using /metrics path across the eco system.
What did you expect to happen:
When we scrape metrics from prometheus using /metrics/ path as per docs we are able to get the metrics. But I feel the slash at the end should not a compulsion which is even making user confusing while configuring.
Hope this is considered as in this ecosystem /metrics path should get the metrics without much efforts in customising the path.
How do we reproduce it?
Grafana OnCall Version
v1.3.80
Product Area
Alert Flow & Configuration, Helm
Grafana OnCall Platform?
Kubernetes
User's Browser?
No response
Anything else to add?
No response
The text was updated successfully, but these errors were encountered: