anchor.diff:  
   image::kubernetes-dashboard-default.png[]
   
  +
   Click on `Nodes` to see a textual representation about the nodes running in the cluster:
   
   image::monitoring-nodes-before.png[]
   
  +
   Install a Java application as explained in link:../helm[Deploying applications using Kubernetes Helm charts].
   
   Click on `Pods`, again to see a textual representation about the pods running in the cluster:
   
   image::monitoring-pods-before.png[]
   
  +
   This will change after Heapster, InfluxDB and Grafana are installed.
   
   == Heapster, InfluxDB and Grafana
   
  -https://github.com/kubernetes/heapster[Heapster] is a metrics aggregator and processor. It is installed as a cluster-wide pod. It gathers monitoring and events data for all containers on each node by talking to the Kubelet. Kubelet itself fetches this data from https://github.com/google/cadvisor[cAdvisor]. This data is persisted in a time series database https://github.com/influxdata/influxdb[InfluxDB] for storage. The data is then visualized using a using http://grafana.org/[Grafana] dashboard or can be viewed in Kubernetes Dashboard.
  -
  -Heapster collects and interprets various signals like compute resource usage, lifecycle events, etc, and exports cluster metrics via REST endpoints.
  +https://github.com/kubernetes/heapster[Heapster] is a metrics aggregator and processor. It is installed as a cluster-wide pod. It gathers monitoring and events data for all containers on each node by talking to the Kubelet. Kubelet itself fetches this data from https://github.com/google/cadvisor[cAdvisor]. This data is persisted in a time series database https://github.com/influxdata/influxdb[InfluxDB] for storage. The data is then visualized using a http://grafana.org/[Grafana] dashboard, or it can be viewed in Kubernetes Dashboard.
  +
  +Heapster collects and interprets various signals like compute resource usage, lifecycle events, etc., and exports cluster metrics via REST endpoints.
   
   Heapster, InfluxDB and Grafana are http://kubernetes.io/docs/admin/addons/[Kubernetes addons].
   
  
positive.code: 
    kubectl describe pod/etcd-server-ip-172-20-43-222.us-west-2.compute.internal --namespace=kube-system 
  
  The output is like:
  
  ```
  Name:         etcd-server-ip-172-20-43-222.us-west-2.compute.internal
  
negative.code: 
  === Grafana dashboard
  
  Grafana dashboard, accessible at http://localhost:8001/api/v1/proxy/namespaces/default/services/grafana/, now shows the information about the cluster.
  
  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`.
  
  