anchor.diff:  ====
   endif::[]
   
  -
  -You will need to save your completed file with the file name *_metrics.yaml_*.
  +In case you need to make any changes to this file, copy it to another directory
  +with the file name *_metrics-deployer.yaml_* and refer to the new location when
  +using it in the following sections.
   
   [[deployer-template-parameters]]
   ==== Deployer Template Parameters
   
  -The deployer template parameter options and their defaults are listed above in
  -the *_metrics.yaml_* file. If required, you can override these values when
  -creating the *metrics deployer*.
  +The deployer template parameter options and their defaults are listed in the
  +default *_metrics-deployer.yaml_* file. If required, you can override these
  +values when creating the Metrics Deployer.
   
   The only required parameter is `*HAWKULAR_METRICS_HOSTNAME*`. This value is
   required when creating the deployer because it specifies the hostname for the
  
positive.code: <1> The value specified in the *HAWKULAR_METRICS_HOSTNAME* template parameter.
  <2> These need to define the custom certificate you wish to provide.
  <3> This needs to correspond to the CA used to sign the internal Hawkular Metrics certificate
  
  The CA used to sign the internal Hawkular Metrics certificate can be found from the
  *hawkular-metrics-certificate* secret:
  
  [options="nowrap"]
  ----
  $ base64 -d <<< `oc get -o yaml secrets hawkular-metrics-certificate | grep -i hawkular-metrics-ca.certificate | awk '{print $2}'`
  ----
  
  
  
  [[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-config.yaml]
  file. This URL corresponds to the route created with the
  `*HAWKULAR_METRICS_HOSTNAME*` template parameter during the
  link:../install_config/cluster_metrics.html#deploying-the-metric-components[deployment]
  of the metrics components.
  
  [NOTE]
  
negative.code: ====
  The following command sets the Hawkular Metrics route to use
  `hawkular-metrics.example.com` and is deployed without persistent storage.
  Remember, this is being deployed without persistent storage, so metrics data loss
  can occur.
  
  ----
  $ oc process -f metrics-deployer.yaml -v \
      HAWKULAR_METRICS_HOSTNAME=hawkular-metrics.example.com,USE_PERSISTENT_STORAGE=false \
      | oc create -f -
  ----
  ====
  
  [[metrics-reencrypting-route]]
  == Using a Re-encrypting Route
  
  [NOTE]
  ====
  The following section is not required if the *hawkular-metrics.pem* secret was
  specified as a
  link:../install_config/cluster_metrics.html#metrics-deployer-using-secrets[deployer
  secret].
  ====
  
  By default, the Hawkular Metrics server uses self-signed certificates, which are
  not trusted by a browser or other external services. If you want to provide your
  own trusted certificate to be used for external access, you can do so using a
  route with a
  link:../architecture/core_concepts/routes.html#secured-routes[re-encryption
  termination] after deploying the metrics components.
  
  . First, delete the default route that uses the self-signed certificates:
  +
  ----
  $ oc delete route hawkular-metrics
  ----
  
  . Define a new route with a
  link:../architecture/core_concepts/routes.html#secured-routes[re-encryption
  termination]:
  +
  ====
  [source,yaml]
  ----
  apiVersion: v1
  