anchor.diff:  
   NOTE: Grafana dashboard will not be available if Kubernetes proxy is not running. If not running, then it can be started with the command `kubectl proxy`.
   
  -=== Grafana dashboards
  +=== Grafana dashboard
   
   There are some built-in dashboards for monitoring the cluster and workloads. They are available by clicking on the upper left corner of the screen.
   
  
positive.code: 
  ```
  NAME                                                                  READY     STATUS    RESTARTS   AGE
  etcd-server-events-ip-172-20-48-121.us-west-2.compute.internal        1/1       Running   0          10h
  etcd-server-ip-172-20-48-121.us-west-2.compute.internal               1/1       Running   0          9h
  ```
  
  Other pods are shown as well, but we are only showing the etcd pods. Note down the name of the pod that starts with `etcd-server-ip`. Get more details about this pod:
  
    kubectl describe pod/etcd-server-ip-172-20-48-121.us-west-2.compute.internal --namespace=kube-system 
  
  The output is like:
  
  ```
  Name:         etcd-server-ip-172-20-48-121.us-west-2.compute.internal
  Namespace:    kube-system
  Node:         ip-172-20-48-121.us-west-2.compute.internal/172.20.48.121
  Start Time:   Wed, 18 Oct 2017 03:09:53 +0200
  Labels:       k8s-app=etcd-server
  Annotations:  kubernetes.io/config.hash=29e2e50ee6b1cd5c2f410da0f8c0f295
                kubernetes.io/config.mirror=29e2e50ee6b1cd5c2f410da0f8c0f295
                kubernetes.io/config.seen=2017-10-18T01:09:48.793098897Z
                kubernetes.io/config.source=file
  Status:       Running
  IP:           172.20.48.121
  
  . . .
  
  
negative.code: 
  image::monitoring-pods-after.png[]
  
  === Cleanup
  
  Remove all the installed components:
  
      kubectl delete -f heapster/templates/
  
  == Prometheus, Node exporter and Grafana
  
  http://prometheus.io/[Prometheus] is an open-source systems monitoring and alerting toolkit. Prometheus collects metrics from monitored targets by scraping metrics from HTTP endpoints on these targets.
  
  Different targets to scrape are defined in a Prometheus configuration file. Targets may be statically configured via the `static_configs` parameter in the configuration fle or dynamically discovered using one of the supported service-discovery mechanisms (Consul, DNS, Etcd, etc.).
  
  https://github.com/prometheus/node_exporter[Node exporter] is a Prometheus exporter for hardware and OS metrics exposed by *NIX kernels.
  
  === Installation
  
  Prometheus configuration file is defined as a ConfigMap in the file `prometheus/templates/prometheus-configmap.yaml`. 
  