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

Prometheus fails to scrape internal metrics since 0.118 #1655

Closed
vinzent opened this issue Feb 13, 2025 · 1 comment
Closed

Prometheus fails to scrape internal metrics since 0.118 #1655

vinzent opened this issue Feb 13, 2025 · 1 comment

Comments

@vinzent
Copy link
Contributor

vinzent commented 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 :

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.

@vinzent 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
@atoulme
Copy link
Contributor

atoulme commented Feb 22, 2025

Please open a support ticket to get help. Issues are not monitored and only kept around for archival.

@atoulme atoulme closed this as not planned Won't fix, can't repro, duplicate, stale Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants