The kubelet exposes metrics that can be collected and stored in back-ends by Heapster.

As an OpenShift Origin administrator, you can view a cluster’s metrics from all containers and components in one user interface. These metrics are also used by horizontal pod autoscalers in order to determine when and how to scale.

This topic describes using Hawkular Metrics as a metrics engine which stores the data persistently in a Cassandra database. When this is configured, CPU, memory and network-based metrics are viewable from the OpenShift Origin web console and are available for use by horizontal pod autoscalers.

Heapster retrieves a list of all nodes from the master server, then contacts each node individually through the /stats endpoint. From there, Heapster scrapes the metrics for CPU, memory and network usage, then exports them into Hawkular Metrics.

Browsing individual pods in the web console displays separate sparkline charts for memory and CPU. The time range displayed is selectable, and these charts automatically update every 30 seconds. If there are multiple containers on the pod, then you can select a specific container to display its metrics.

If resource limits are defined for your project, then you can also see a donut chart for each pod. The donut chart displays usage against the resource limit. For example: 145 Available of 200 MiB, with the donut chart showing 55 MiB Used.

For more information about the metrics integration, please refer to the Origin Metrics GitHub project.

Before You Begin

If your OpenShift Origin installation was originally performed on a version previous to v1.0.8, even if it has since been updated to a newer version, follow the instructions for node certificates outlined in Updating Master and Node Certificates. If the node certificate does not contain the IP address of the node, then Heapster will fail to retrieve any metrics.

An Ansible playbook is available to deploy and upgrade cluster metrics. You should familiarize yourself with the Advanced Installation section. This provides information for prepairing to use Ansible and includes information about configuration. Parameters are added to the Ansible inventory file to configure various areas of cluster metrics.

The following describe the various areas and the parameters that can be added to the Ansible inventory file in order to modify the defaults:

Metrics Project

The components for cluster metrics must be deployed to the openshift-infra project in order for autoscaling to work. Horizontal pod autoscalers specifically use this project to discover the Heapster service and use it to retrieve metrics. The metrics project can be changed by adding openshift_metrics_project to the inventory file.

Metrics Data Storage

You can store the metrics data to either persistent storage or to a temporary pod volume.

Persistent Storage

Running OpenShift Origin cluster metrics with persistent storage means that your metrics will be stored to a persistent volume and be able to survive a pod being restarted or recreated. This is ideal if you require your metrics data to be guarded from data loss. For production environments it is highly recommended to configure persistent storage for your metrics pods.

The size requirement of the Cassandra storage is dependent on the number of pods. It is the administrator’s responsibility to ensure that the size requirements are sufficient for their setup and to monitor usage to ensure that the disk does not become full. The size of the persisted volume claim is specified with the openshift_metrics_cassandra_pvc_size ansible variable which is set to 10 GB by default.

If you would like to use dynamically provisioned persistent volumes set the openshift_metrics_cassandra_storage_type variable to dynamic in the inventory file.

Capacity Planning for Cluster Metrics

After running the openshift_metrics Ansible role, the output of oc get pods should resemble the following:

 # oc get pods -n openshift-infra
 NAME                                READY             STATUS      RESTARTS          AGE
 hawkular-cassandra-1-l5y4g          1/1               Running     0                 17h
 hawkular-metrics-1t9so              1/1               Running     0                 17h
 heapster-febru                      1/1               Running     0                 17h

OpenShift Origin metrics are stored using the Cassandra database, which is deployed with settings of openshift_metrics_cassandra_limits_memory: 2G; this value could be adjusted further based upon the available memory as determined by the Cassandra start script. This value should cover most OpenShift Origin metrics installations, but using environment variables you can modify the MAX_HEAP_SIZE along with heap new generation size, HEAP_NEWSIZE, in the Cassandra Dockerfile prior to deploying cluster metrics.

By default, metrics data is stored for seven days. After seven days, Cassandra begins to purge the oldest metrics data. Metrics data for deleted pods and projects is not automatically purged; it is only removed once the data is more than seven days old.

Example 1. Data Accumulated by 10 Nodes and 1000 Pods

In a test scenario including 10 nodes and 1000 pods, a 24 hour period accumulated 2.5 GB of metrics data. Therefore, the capacity planning formula for metrics data in this scenario is:

(((2.5 × 109) ÷ 1000) ÷ 24) ÷ 106 = ~0.125 MB/hour per pod.

Example 2. Data Accumulated by 120 Nodes and 10000 Pods

In a test scenario including 120 nodes and 10000 pods, a 24 hour period accumulated 25 GB of metrics data. Therefore, the capacity planning formula for metrics data in this scenario is:

(((11.410 × 109) ÷ 1000) ÷ 24) ÷ 106 = 0.475 MB/hour

1000 pods 10000 pods

Cassandra storage data accumulated over 24 hours (default metrics parameters)

2.5 GB

11.4 GB

These two test cases are presented on the following graph:

1000 pods vs 10000 pods monitored during 24 hours

If the default value of 7 days for openshift_metrics_duration and 10 seconds for openshift_metrics_resolution are preserved, then weekly storage requirements for the Cassandra pod would be:

1000 pods 10000 pods

Cassandra storage data accumulated over seven days (default metrics parameters)

20 GB

90 GB

In the previous table, an additional 10 percent was added to the expected storage space as a buffer for unexpected monitored pod usage.

If the Cassandra persisted volume runs out of sufficient space, then data loss will occur.

For cluster metrics to work with persistent storage, ensure that the persistent volume has the ReadWriteOnce access mode. If this mode is not active, then the persistent volume claim cannot locate the persistent volume, and Cassandra fails to start.

To use persistent storage with the metric components, ensure that a persistent volume of sufficient size is available. The creation of persistent volume claims is handled by the OpenShift Ansible openshift_metrics role.

OpenShift Origin metrics also supports dynamically-provisioned persistent volumes. To use this feature with OpenShift Origin metrics, it is necessary to set the value of openshift_metrics_cassandra_storage_type to dynamic. You can use EBS, GCE, and Cinder storage back-ends to dynamically provision persistent volumes.

For information on configuring the performance and scaling the cluster metrics pods, see the Scaling Cluster Metrics topic.

Known Issues and Limitations

Testing found that the heapster metrics component is capable of handling up to 25,000 pods. If the amount of pods exceed that number, Heapster begins to fall behind in metrics processing, resulting in the possibility of metrics graphs no longer appearing. Work is ongoing to increase the number of pods that Heapster can gather metrics on, as well as upstream development of alternate metrics-gathering solutions.

Non-Persistent Storage

Running OpenShift Origin cluster metrics with non-persistent storage means that any stored metrics will be deleted when the pod is deleted. While it is much easier to run cluster metrics with non-persistent data, running with non-persistent data does come with the risk of permanent data loss. However, metrics can still survive a container being restarted.

In order to use non-persistent storage, you must set the openshift_metrics_cassandra_storage_type variable to emptyDir in the inventory file.

When using non-persistent storage, metrics data will be written to /var/lib/origin/openshift.local.volumes/pods on the node where the Cassandra pod is running. Ensure /var has enough free space to accommodate metrics storage.

Metrics Ansible Role

The OpenShift Ansible openshift_metrics role configures and deploys all of the metrics components using the variables from the Configuring Ansible inventory file.

Specifying Metrics Ansible Variables

The openshift_metrics role included with OpenShift Ansible defines the tasks to deploy cluster metrics. The following is a list of role variables that can be added to your inventory file if it is necessary to override them.

Table 1. Ansible Variables
Variable Description


Deploy metrics if true. Otherwise, undeploy.


Start the metrics cluster after deploying the components.


The prefix for the component images. With openshift/origin-metrics-cassandra:v1.3, set prefix openshift/origin-.


The version for the component images. For example, with openshift/origin-metrics-cassandra:v1.3, set version as v1.3.


The time, in seconds, to wait until Hawkular Metrics and Heapster start up before attempting a restart.


The number of days to store metrics before they are purged.


The frequency that metrics are gathered. Defined as a number and time identifier: seconds (s), minutes (m), hours (h).


The persistent volume claim prefix created for Cassandra. A serial number is appended to the prefix starting from 1.


The persistent volume claim size for each of the Cassandra nodes.


Use emptyDir for ephemeral storage (for testing); pv for persistent volumes, which need to be created before the installation; or dynamic for dynamic persistent volumes.


The number of Cassandra nodes for the metrics stack. This value dictates the number of Cassandra replication controllers.


The memory limit for the Cassandra pod. For example, a value of 2Gi would limit Cassandra to 2 GB of memory. This value could be further adjusted by the start script based on available memory of the node on which it is scheduled.


The CPU limit for the Cassandra pod. For example, a value of 4000m (4000 millicores) would limit Cassandra to 4 CPUs.


The number of replicas for Cassandra.


The amount of memory to request for Cassandra pod. For example, a value of 2Gi would request 2 GB of memory.


The CPU request for the Cassandra pod. For example, a value of 4000m (4000 millicores) would request 4 CPUs.


The supplemental storage group to use for Cassandra.


Set to the desired, existing node selector to ensure that pods are placed onto nodes with specific labels. For example, {"region":"infra"}.


An optional certificate authority (CA) file used to sign the Hawkular certificate.


The certificate file used for re-encrypting the route to Hawkular metrics. The certificate must contain the host name used by the route. If unspecified, the default router certificate is used.


The key file used with the Hawkular certificate.


The amount of memory to limit the Hawkular pod. For example, a value of 2Gi would limit the Hawkular pod to 2 GB of memory. This value could be further adjusted by the start script based on available memory of the node on which it is scheduled.


The CPU limit for the Hawkular pod. For example, a value of 4000m (4000 millicores) would limit the Hawkular pod to 4 CPUs.


The number of replicas for Hawkular metrics.


The amount of memory to request for the Hawkular pod. For example, a value of 2Gi would request 2 GB of memory.


The CPU request for the Hawkular pod. For example, a value of 4000m (4000 millicores) would request 4 CPUs.


Set to the desired, existing node selector to ensure that pods are placed onto nodes with specific labels. For example, {"region":"infra"}.


A comma-separated list of CN to accept. By default, this is set to allow the OpenShift service proxy to connect. Add system:master-proxy to the list when overriding in order to allow horizontal pod autoscaling to function properly.


The amount of memory to limit the Heapster pod. For example, a value of 2Gi would limit the Heapster pod to 2 GB of memory.


The CPU limit for the Heapster pod. For example, a value of 4000m (4000 millicores) would limit the Heapster pod to 4 CPUs.


The amount of memory to request for Heapster pod. For example, a value of 2Gi would request 2 GB of memory.


The CPU request for the Heapster pod. For example, a value of 4000m (4000 millicores) would request 4 CPUs.


Deploy only Heapster, without the Hawkular Metrics and Cassandra components.


Set to the desired, existing node selector to ensure that pods are placed onto nodes with specific labels. For example, {"region":"infra"}.


Set to true to install the Hawkular OpenShift Agent (HOSA). Set to false to remove the HOSA from an installation. HOSA can be used to collect custom metrics from your pods. This component is currently in Technology Preview and is not installed by default.

The Hawkular OpenShift Agent on OpenShift Origin is a Technology Preview feature only.

See Compute Resources for further discussion on how to specify requests and limits.

The only required variable is openshift_metrics_hawkular_hostname. This value is required when executing the openshift_metrics Ansible role because it uses the host name for the Hawkular Metrics route. This value should correspond to a fully qualified domain name. You must know the value of openshift_metrics_hawkular_hostname when configuring the console for metrics access.

If you are using persistent storage with Cassandra, it is the administrator’s responsibility to set a sufficient disk size for the cluster using the openshift_metrics_cassandra_pvc_size variable. It is also the administrator’s responsibility to monitor disk usage to make sure that it does not become full.

Data loss will result if the Cassandra persisted volume runs out of sufficient space.

All of the other variables are optional and allow for greater customization. For instance, if you have a custom install in which the Kubernetes master is not available under https://kubernetes.default.svc:443 you can specify the value to use instead with the openshift_metrics_master_url parameter. To deploy a specific version of the metrics components, modify the openshift_metrics_image_version variable.

It is highly recommended to not use latest for the openshift_metrics_image_version. The latest version corresponds to the very latest version available and can cause issues if it brings in a newer version not meant to function on the version of OpenShift Origin you are currently running.

Using Secrets

The OpenShift Ansible openshift_metrics role will auto-generate self-signed certificates for use between its components and will generate a re-encrypting route to expose the Hawkular Metrics service. This route is what allows the web console to access the Hawkular Metrics service.

In order for the browser running the web console to trust the connection through this route, it must trust the route’s certificate. This can be accomplished by providing your own certificates signed by a trusted Certificate Authority. The openshift_metrics role allows you to specify your own certificates which it will then use when creating the route.

The router’s default certificate are used if you do not provide your own.

Providing Your Own Certificates

To provide your own certificate which will be used by the re-encrypting route, you can set the openshift_metrics_hawkular_cert, openshift_metrics_hawkular_key, and openshift_metrics_hawkular_ca variables in your inventory file.

The hawkular-metrics.pem value needs to contain the certificate in its .pem format. You may also need to provide the certificate for the Certificate Authority which signed this pem file via the hawkular-metrics-ca.cert secret.

For more information, please see the re-encryption route documentation.

Deploying the Metric Components

Because deploying and configuring all the metric components is handled with OpenShift Ansible, you can deploy everything in one step.

The following examples show you how to deploy metrics with and without persistent storage using the default parameters.

Example 3. Deploying with Persistent Storage

The following command sets the Hawkular Metrics route to use hawkular-metrics.example.com and is deployed using persistent storage.

You must have a persistent volume of sufficient size available.

$ ansible-playbook <OPENSHIFT_ANSIBLE_DIR>/byo/openshift-cluster/openshift-metrics.yml \
   -e openshift_metrics_install_metrics=True \
   -e openshift_metrics_hawkular_hostname=hawkular-metrics.example.com \
   -e openshift_metrics_cassandra_storage_type=pv
Example 4. Deploying without Persistent Storage

The following command sets the Hawkular Metrics route to use hawkular-metrics.example.com and deploy without persistent storage.

$ ansible-playbook <OPENSHIFT_ANSIBLE_DIR>/byo/openshift-cluster/openshift-metrics.yml \
   -e openshift_metrics_install_metrics=True \
   -e openshift_metrics_hawkular_hostname=hawkular-metrics.example.com

Because this is being deployed without persistent storage, metric data loss can occur.

Metrics Diagnostics

The are some diagnostics for metrics to assist in evaluating the state of the metrics stack. To execute diagnostics for metrics:

$ oadm diagnostics MetricsApiProxy

Setting the Metrics Public URL

The OpenShift Origin web console uses the data coming from the Hawkular Metrics service to display its graphs. The URL for accessing the Hawkular Metrics service must be configured with the metricsPublicURL option in the master configuration file (/etc/origin/master/master-config.yaml). This URL corresponds to the route created with the openshift_metrics_hawkular_hostname inventory variable used during the deployment of the metrics components.

You must be able to resolve the openshift_metrics_hawkular_hostname from the browser accessing the console.

For example, if your openshift_metrics_hawkular_hostname corresponds to hawkular-metrics.example.com, then you must make the following change in the master-config.yaml file:

    metricsPublicURL: "https://hawkular-metrics.example.com/hawkular/metrics"

Once you have updated and saved the master-config.yaml file, you must restart your OpenShift Origin instance.

When your OpenShift Origin server is back up and running, metrics will be displayed on the pod overview pages.

If you are using self-signed certificates, remember that the Hawkular Metrics service is hosted under a different host name and uses different certificates than the console. You may need to explicitly open a browser tab to the value specified in metricsPublicURL and accept that certificate.

To avoid this issue, use certificates which are configured to be acceptable by your browser.

Accessing Hawkular Metrics Directly

To access and manage metrics more directly, use the Hawkular Metrics API.

When accessing Hawkular Metrics from the API, you will only be able to perform reads. Writing metrics has been disabled by default. If you want for individual users to also be able to write metrics, you must set the openshift_metrics_hawkular_user_write_access variable to true.

However, it is recommended to use the default configuration and only have metrics enter the system via Heapster. If write access is enabled, any user will be able to write metrics to the system, which can affect performance and cause Cassandra disk usage to unpredictably increase.

The Hawkular Metrics documentation covers how to use the API, but there are a few differences when dealing with the version of Hawkular Metrics configured for use on OpenShift Origin:

OpenShift Origin Projects and Hawkular Tenants

Hawkular Metrics is a multi-tenanted application. It is configured so that a project in OpenShift Origin corresponds to a tenant in Hawkular Metrics.

As such, when accessing metrics for a project named MyProject you must set the Hawkular-Tenant header to MyProject.

There is also a special tenant named _system which contains system level metrics. This requires either a cluster-reader or cluster-admin level privileges to access.


The Hawkular Metrics service will authenticate the user against OpenShift Origin to determine if the user has access to the project it is trying to access.

Hawkular Metrics accepts a bearer token from the client and verifies that token with the OpenShift Origin server using a SubjectAccessReview. If the user has proper read privileges for the project, they are allowed to read the metrics for that project. For the _system tenant, the user requesting to read from this tenant must have cluster-reader permission.

When accessing the Hawkular Metrics API, you must pass a bearer token in the Authorization header.

Accessing Heapster Directly

Heapster has been configured to be only accessible via the API proxy. Accessing it will required either a cluster-reader or cluster-admin privileges.

For example, to access the Heapster validate page, you need to access it using something similar to:

$ curl -H "Authorization: Bearer XXXXXXXXXXXXXXXXX" \
       -X GET https://${KUBERNETES_MASTER}/api/v1/proxy/namespaces/openshift-infra/services/https:heapster:/validate

For more information about Heapster and how to access its APIs, please refer the Heapster project.

Scaling OpenShift Origin Cluster Metrics Pods

Information about scaling cluster metrics capabilities is available in the Scaling and Performance Guide.

Integration with Aggregated Logging

Hawkular Alerts must be connected to the Aggregated Logging’s Elasticsearch to react on log events. By default, Hawkular will try to find Elasticsearch on its default place (namespace logging, pod logging-es) at every boot. If the Aggregated Logging is installed after Hawkular, the Hawkular Metrics pod might need to be restarted in order to recognize the new Elasticsearch server. The Hawkular boot log provides a clear indication if the integration could not be properly configured, with messages like:

Failed to import the logging certificate into the store. Continuing, but the logging integration might fail. ---


Could not get the logging secret! Status code: 000. The Hawkular Alerts integration with Logging might not work properly. ---

This feature is available from version v1.7. You can confirm if logging is available by checking the log for an entry like:

Retrieving the Logging’s CA and adding to the trust store, if Logging is available. ---


You can remove everything deployed by the OpenShift Ansible openshift_metrics role by performing the following steps:

$ ansible-playbook <OPENSHIFT_ANSIBLE_DIR>/byo/openshift-cluster/openshift-metrics.yml \
   -e openshift_metrics_install_metrics=False

Prometheus on OpenShift Origin

Prometheus is a stand-alone, open source systems monitoring and alerting toolkit. You can use Prometheus to visualize metrics and alerts for OpenShift Origin system resources.

Prometheus on OpenShift is a Technology Preview feature only.

Setting Prometheus Role Variables

The Prometheus role creates:

  • The openshift-metrics namespace.

  • Prometheus clusterrolebinding and service account.

  • Prometheus pod with Prometheus behind OAuth proxy, Alertmanager, and Alert Buffer as a stateful set.

  • Prometheus and prometheus-alerts ConfigMaps.

  • Prometheus and Prometheus Alerts services and direct routes.

Prometheus deployment is disabled by default, enable it by setting openshift_hosted_prometheus_deploy to true. For example:

# openshift_hosted_prometheus_deploy=true

Set the following role variables to install and configure Prometheus.

Table 2. Prometheus Variables
Variable Description


Project namespace where the components are deployed. Default set to openshift-metrics. For example, openshift_prometheus_namespace=${USER_PROJECT}.


Selector for the nodes on which Prometheus is deployed.


Set to create PV for Prometheus. For example, openshift_prometheus_storage_kind=nfs.


Set to create PV for Alertmanager. For example, openshift_prometheus_alertmanager_storage_kind=nfs.


Set to create PV for Alert Buffer. For example, openshift_prometheus_alertbuffer_storage_kind=nfs.


Set to create PVC for Prometheus. For example, openshift_prometheus_storage_type=pvc.


Set to create PVC for Alertmanager. For example, openshift_prometheus_alertmanager_storage_type=pvc.


Set to create PVC for Alert Buffer. For example, openshift_prometheus_alertbuffer_storage_type=pvc.


Additional Prometheus rules file. Set to null by default.

Deploying Prometheus Using Ansible Installer

The Ansible Installer is the default method of deploying Prometheus.

Add label to your node:

# Inventory file


Run the playbook:

$ ansible-playbook -vvv -i ${INVENTORY_FILE} playbooks/byo/openshift-cluster/openshift-prometheus.yml

Additional Methods for Deploying Prometheus

Deploy Using Node-Selector

Label the node on which you want to deploy Prometheus:

# oadm label node/$NODE ${KEY}=${VALUE}

Deploy Prometheus with Ansible and container resources:

# Inventory file

# Set node selector for prometheus

Run the playbook:

$ ansible-playbook -vvv -i ${INVENTORY_FILE} playbooks/byo/openshift-cluster/openshift-prometheus.yml

Deploy Using a Non-default Namespace

Identify your namespace:

# Inventory file

# Set non-default openshift_prometheus_namespace

Run the playbook:

$ ansible-playbook -vvv -i ${INVENTORY_FILE} playbooks/byo/openshift-cluster/openshift-prometheus.yml

Accessing the Prometheus Web UI

The Prometheus server automatically exposes a Web UI at localhost:9090. You can access the Prometheus Web UI with the view role.

Configuring Prometheus for OpenShift

Example Prometheus rules file:

# additional prometheus rules file
openshift_prometheus_additional_rules_file: null

# All the required exports
-  prometheus
-  prometheus-alertmanager
-  prometheus-alertbuffer
# PV template files and their created object names
  -  pv_name: prometheus
     pv_template: prom-pv-server.yml
     pv_label: Prometheus Server PV
  -  pv_name: prometheus-alertmanager
     pv_template: prom-pv-alertmanager.yml
     pv_label: Prometheus Alertmanager PV
  -  pv_name: prometheus-alertbuffer
     pv_template: prom-pv-alertbuffer.yml
     pv_label: Prometheus Alert Buffer PV

# Hostname/IP of the NFS server.

# storage
openshift_prometheus_storage_type: pvc
openshift_prometheus_pvc_name: prometheus
openshift_prometheus_pvc_size: 10G
openshift_prometheus_pvc_access_modes: [ReadWriteOnce]
openshift_prometheus_pvc_pv_selector: {}

openshift_prometheus_alertmanager_storage_type: pvc
openshift_prometheus_alertmanager_pvc_name: prometheus-alertmanager
openshift_prometheus_alertmanager_pvc_size: 10G
openshift_prometheus_alertmanager_pvc_access_modes: [ReadWriteOnce]
openshift_prometheus_alertmanager_pvc_pv_selector: {}
openshift_prometheus_cpu_limit: null
openshift_prometheus_memory_limit: null
openshift_prometheus_cpu_requests: null
openshift_prometheus_memory_requests: null
openshift_prometheus_alertmanager_cpu_limit: null
openshift_prometheus_alertmanager_memory_limit: null
openshift_prometheus_alertmanager_cpu_requests: null
openshift_prometheus_alertmanager_memory_requests: null
openshift_prometheus_alertbuffer_cpu_limit: null
openshift_prometheus_alertbuffer_memory_limit: null
openshift_prometheus_alertbuffer_cpu_requests: null
openshift_prometheus_alertbuffer_memory_requests: null
openshift_prometheus_oauth_proxy_cpu_limit: null
openshift_prometheus_oauth_proxy_memory_limit: null
openshift_prometheus_oauth_proxy_cpu_requests: null
openshift_prometheus_oauth_proxy_memory_requests: null

Prometheus Storage Related Variables

With each Prometheus component (including Prometheus, Alertmanager, Alert Buffer, and OAuth proxy) you can set the PV claim by setting corresponding role variable, for example:

openshift_prometheus_storage_type: pvc
openshift_prometheus_alertmanager_pvc_name: alertmanager
openshift_prometheus_alertbuffer_pvc_size: 10G
openshift_prometheus_pvc_access_modes: [ReadWriteOnce]

Prometheus Alert Rules File Variable

You can add an external file with alert rules by setting the path to an additional rules variable:

openshift_prometheus_additional_rules_file: <PATH>

The file content should be in Prometheus Alert rules format. The following example sets a rule to send an alert when one of the cluster nodes is down:

- name: example-rules
  interval: 30s # defaults to global interval
  - alert: Node Down
    expr: up{job="kubernetes-nodes"} == 0
      miqTarget: "ContainerNode"
      severity: "HIGH"
      message: "{{ '{{' }}{{ '$labels.instance' }}{{ '}}' }} is down"

Prometheus Variables to Control Resource Limits

With each Prometheus component (including Prometheus, Alertmanager, Alert Buffer, and OAuth proxy) you can specify CPU, memory limits, and requests by setting the corresponding role variable, for example:

openshift_prometheus_alertmanager_limits_memory: 1Gi
openshift_prometheus_oauth_proxy_cpu_requests: 100m

For more detailed information, see OpenShift Prometheus.

Metrics can be gathered from the http://${POD_IP}:7575/metrics endpoint.

Undeploying Prometheus

To undeploy Prometheus, run:

$ ansible-playbook -vvv -i ${INVENTORY_FILE} playbooks/byo/openshift-cluster/openshift-prometheus.yml