anchor.diff:  link:../install_config/cluster_metrics.html#configuring-openshift-metrics[configuring
   the console] for metrics access.
   
  -If you are using link:..install_config/cluster_metrics.html#metrics-persistent-storage[persistent storage]
  -with Cassandra it is the admin's responsibility to set a sufficient disk size for the cluster using
  -the `*CASSANDRA_PV_SIZE*` parameter. It is also the admin's responsibility to monitor disk usage to make
  -sure that it does not become full.
  +If you are using
  +link:../install_config/cluster_metrics.html#metrics-persistent-storage[persistent
  +storage] with Cassandra, it is the administrator's responsibility to set a
  +sufficient disk size for the cluster using the `*CASSANDRA_PV_SIZE*` parameter.
  +It is also the administrator's responsibility to monitor disk usage to make sure
  +that it does not become full.
   
   [WARNING]
   ====
  -*Data loss will result if the Cassandra persisted volume runs out of sufficient space.*
  +Data loss will result if the Cassandra persisted volume runs out of sufficient space.
   ====
   
   All of the other parameters are optional and allow for greater customization.
  
positive.code: [[configuring-openshift-metrics]]
  == Configuring OpenShift
  
  The OpenShift 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 via the `*metricsPublicURL*` option in the
  link:../install_config/master_node_configuration.html#master-configuration-files[master
  configuration file] (*_/etc/origin/master/master-config.yaml_*). This URL
  corresponds to the route created with the `*HAWKULAR_METRICS_HOSTNAME*` template
  
negative.code: ifdef::openshift-origin[]
  == Accessing Hawkular Metrics Directly
  
  If you wish to access and manage metrics more directly, you can do so via the
  Hawkular Metrics API.
  
  The link:http://www.hawkular.org/docs/rest/rest-metrics.html[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
  {product-title}:
  
  === OpenShift Projects & Hawkular Tenants
  
  Hawkular Metrics is a multi-tenanted application. The way its been configured is
  that a project in {product-title} corresponds to a tenant in Hawkular Metrics.
  
  As such, when accessing metrics for a project named `MyProject` you will need to
  set the
  link:http://www.hawkular.org/docs/rest/rest-metrics.html#_tenant_header[Hawkular-tenant]
  header to `MyProject`
  
  There is also a special tenant named `_system` which contains system level
  metrics. This will require either a `cluster-reader` or `cluster-admin` level
  privileges to access.
  
  === Authorization
  
  The Hawkular Metrics service will authenticate the user against {product-title}
  to determine if the user has access to the project it is trying to access.
  
  When accessing the Hawkular Metrics API, you will need to pass a bearer token in
  the `Authorization` header.
  
  For more information how how to access the Hawkular Metrics in {product-title},
  please see the
  link:https://github.com/openshift/origin-metrics/blob/master/docs/hawkular_metrics.adoc[Origin
  Metrics documentation]
  
  == Accessing Heapster Directly
  
  Heapster has been configured to be only accessible via the
  link:../rest_api/kubernetes_v1.html#proxy-get-requests-to-service[API proxy].
  Accessing it will required either a cluster-reader or cluster-admin privileges.
  
  For example, to access the Heapster `validate` page, you would need to access it
  using something similar to:
  
  ----
  $ curl -H "Authorization: Bearer XXXXXXXXXXXXXXXXX" \
  