anchor.diff:  
   [[exposing-the-router-metrics]]
   
  -=== Expose Router metrics
  -
  -The {product-title} router can optionally be configured to run a sidecar container
  -in the router pod. Depending on the image run in the sidecar container, this
  -provides a mechanism to expose or publish router metrics for consumption by
  -external metrics collection and/or aggregation systems (e.g. Prometheus, statsd).
  -
  -The `--metrics-image` and `--expose-metrics` flags control this
  -above-mentioned behaviour. Depending on the router implementation in use,
  -the image is appropriately setup and the metrics sidecar container is
  -started up when the router is deployed.
  -
  -The HAProxy based router implementation defaults to using the
  -`prom/haproxy-exporter` image to run as a sidecar container, which can then
  -be used as a metrics datasource by the Prometheus server.
  +=== Exposing Router metrics
  +
  +Using the `--metrics-image` and `--expose-metrics` options, you can configure
  +the {product-title} router to run a sidecar container that exposes or publishes
  +router metrics for consumption by external metrics collection and aggregation
  +systems (e.g. Prometheus, statsd). 
  +
  +Depending on your router implementation, the image is appropriately set up and
  +the metrics sidecar container is started when the router is deployed. For
  +example, the HAProxy-based router implementation defaults to using the
  +`prom/haproxy-exporter` image to run as a sidecar container, which can then be
  +used as a metrics datasource by the Prometheus server.
   
   [NOTE]
   ====
  -The `--metrics-image` flag allows you to override the defaults for HAProxy
  -based router implementations and in the case of custom implementations
  -enables the image to use for a custom metrics exporter (or publisher).
  -====
  -
  -
  -ifdef::openshift-enterprise[]
  +The `--metrics-image` option overrides the defaults for HAProxy-based router
  +implementations and, in the case of custom implementations, enables the image to
  +use for a custom metrics exporter or publisher.
  +====
  +
  +ifdef::openshift-enterprise[]
  +. Grab the HAProxy Prometheus exporter image from the Docker registry:
  ++
   ====
   ----
   $ sudo docker pull prom/haproxy-exporter
  -
  +----
  +====
  +
  +. Create the {product-title} router:
  ++
  +====
  +----
   $ oadm router \
       --credentials='/etc/origin/master/openshift-router.kubeconfig' \
       --service-account=router --expose-metrics
  -
  -$ # Same as above - the command arguments show the --metrics-image usage.
  +----
  +====
  ++
  +Or, optionally, use the `--metrics-image` option to override the HAProxy
  +defaults:
  ++
  +====
  +----
   $ oadm router \
       --credentials='/etc/origin/master/openshift-router.kubeconfig' \
       --service-account=router --expose-metrics  \
  
positive.code: ====
  endif::[]
  
  
  Once the haproxy-exporter containers (and your HAProxy router) are started
  up, you can now point Prometheus at the sidecar container (on port 9101 on
  the node where the haproxy-exporter container is running).
  
  An example prometheus config and its usage is show below.
  
  ====
  ----
  $ haproxy_exporter_ip="<enter-ip-address-or-hostname>"
  
negative.code: 
  $ echo "  - Once the prometheus server is up, view the {product-title} HAProxy "
  $ echo "    router metrics at: http://<ip>:9090/consoles/haproxy.html "
  ----
  ====
  
  