anchor.diff:  - job_name: 'etcd'
     target_groups:
     - targets:
  -    - 172.20.48.121:4001
  +    - 172.20.43.222:4001
   ```
   
   TODO: Is this required? Check config map again. etcd is already running in the cluster. etcd clusters deployed with the most recent version of kops use port 4001, if you have a newer version of etcd it will be listening on port 2379.
  
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: - Kubernetes API server: https://github.com/kubernetes/kube-state-metrics
  - Node exporter: https://github.com/prometheus/node_exporter
  
  Let's look at these these metrics in Prometheus dashboard.
  
  . Find a master node in the EC2 console:
  +
  image::prometheus-ec2-nodes.png[]
  +
  . Copy public IP address of the master node as `<master-ip>`.
  . Prometheus dashboard is accessible on the port `30900`. Edit the security group and add a rule to allow inbound traffic on the port 30900 as shown:
  +
  image::prometheus-ec2-security-group.png[]
  +
  . Prometheus dashboard is now available at http://<master-ip>:30900. In our case, this will be http://ec2-54-191-175-245.us-west-2.compute.amazonaws.com:30900, and looks like:
  +
  image::prometheus-dashboard-initial.png[]
  +
  