anchor.diff:  [[metrics-persistent-storage]]
   === Persistent Storage
   
  -Running OpenShift cluster metrics with persistent storage means that your
  -metrics will be stored to a
  + Running {product-title} cluster metrics with persistent storage means that
  +your metrics will be stored to a
   link:../architecture/additional_concepts/storage.html#persistent-volumes[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.
  -
  -The size of the persisted volume can be specified with the `CASSANDRA_PV_SIZE` 
  -link:../install_config/cluster_metrics.html#deployer-template-parameters[template parameter]. 
  -By default it is set to 10 Gigabytes, which may or may not be sufficient for the size of the cluster you are using. 
  -If you require more space, for instance 100 Gigabytes, you could specify it with something like
  -this:
  +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.
  +
  +The size of the persisted volume can be specified with the `CASSANDRA_PV_SIZE`
  +link:../install_config/cluster_metrics.html#deployer-template-parameters[template
  +parameter]. By default it is set to 10 GB, which may or may not be sufficient
  +for the size of the cluster you are using. If you require more space, for
  +instance 100 GB, you could specify it with something like this:
   
   ----
   $ oc process -f metrics-deployer.yaml -v \
  
positive.code: [NOTE]
  ====
  Depending on your installation method, the template may not be present in your
  OpenShift installation. If so, the template can be found at the following GitHub
  location:
  
  https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_examples/files/examples/v1.1/infrastructure-templates/origin/metrics-deployer.yaml
  
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" \
  