You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alternatively, you can expose the Prometheus endpoint to one specific or all network interfaces when needed. For containerized environments, you might want to expose this port on a public interface.
If I change it manually to 0.0.0.0 scraping with the cluster-internal Prometheus works again.
I think this should be configurable to be able to allow access to metrics for Prometheus scraping.
The text was updated successfully, but these errors were encountered:
vinzent
changed the title
Prometheus fails to scrape internal metrics sind 0.118
Prometheus fails to scrape internal metrics since 0.118
Feb 13, 2025
Since we've upgraded to 0.118 (from 0.112) we cannot scrape metrics anymore with our internal cluster monitoring (OpenShift Monitoring, Prometheus).
Seems this is related to the change in #1573 which binds metrics to localhost only.
Reading https://opentelemetry.io/docs/collector/internal-telemetry/#configure-internal-metrics :
If I change it manually to 0.0.0.0 scraping with the cluster-internal Prometheus works again.
I think this should be configurable to be able to allow access to metrics for Prometheus scraping.
The text was updated successfully, but these errors were encountered: