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
I’m currently using the Cluster Observability Operator to create a MonitoringStack in my specific namespace. When I navigate to Developer > Observe, I can write PromQL queries and see all the “kube” labels. However, I would like to scrape these metrics using my own instance of Prometheus, which is deployed by the MonitoringStack.
As I understand it, kube-state-metrics is deployed in the openshift-monitoring namespace and provides provides metrics to all namespaces, but only on GUI. My question is, how can I access these metrics in Prometheus within my own namespace? I’m trying to avoid deploying additional instances of kube-state-metrics in each namespace.
Any guidance or suggestions would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
Hello,
I’m currently using the Cluster Observability Operator to create a MonitoringStack in my specific namespace. When I navigate to Developer > Observe, I can write PromQL queries and see all the “kube” labels. However, I would like to scrape these metrics using my own instance of Prometheus, which is deployed by the MonitoringStack.
As I understand it, kube-state-metrics is deployed in the
openshift-monitoring
namespace and provides provides metrics to all namespaces, but only on GUI. My question is, how can I access these metrics in Prometheus within my own namespace? I’m trying to avoid deploying additional instances of kube-state-metrics in each namespace.Any guidance or suggestions would be greatly appreciated.
The text was updated successfully, but these errors were encountered: