OpenShift Monitoring with Prometheus
search cancel

OpenShift Monitoring with Prometheus


Article ID: 217544


Updated On:


CA Application Performance Management SaaS


We have configured UMA to monitor OpenShift.  We belive it is working as expected.  But, under the Prometheus Performance agent, seeing a Kubernetes node as well as an OpenShift one.  The OpenShift node has only one metric in it.  While the Kubernetes one has everything in it that we would expect would be under the OpenShift node.

What needs to be changed or updated to get only the OpenShift node with all of the metrics and openshift naming?  Like Projects vs Namespaces.


Release : SAAS

Component :


From the Log: The highlighted properties are left blank. 

 [INFO] [IntroscopeAgent.InfrastructureAgent] = 
 [INFO] [IntroscopeAgent.InfrastructureAgent] = 
[INFO] [IntroscopeAgent.InfrastructureAgent] = false
[INFO] [IntroscopeAgent.InfrastructureAgent] = 30
 [INFO] [IntroscopeAgent.InfrastructureAgent] = 
 [INFO] [IntroscopeAgent.InfrastructureAgent] = 


Indicate the list of Ports that should be scrapped in case the Prometheus Deployment is DaemonSet based ( like node-exporter )
# For eg. 1111, 2222 indicates that the data will be scrapped on /metrics end points
# for every node in the cluster
# Default : blank


And we would scrap all URLs on those listening ports

# Comma separated list of URLs that needs to be scrapped
# Default : None