anchor.diff:  Next, start the port-forward:
   
   ....
  -${CCP_CLI?} port-forward <KIBANA POD NAME> 5601:5601
  +${CCP_CLI?} port-forward <KIBANA POD NAME> 5601:5601 -n kube-system
   ....
   
   To access the web dashboard navigate in a browser to `127.0.0.1:5601`.
   
   First, click the `Discover` tab and setup an index pattern to use for queries.
   
  -The index pattern name we will use is `logstash-*` because Fluentd is configured to 
  +The index pattern name we will use is `logstash-*` because Fluentd is configured to
   generate logstash style logs.
   
   Next we will configure the `Time Filter field name` to be `@timestamp`.
  
positive.code: 
  === Centralized Logging
  
  The logs generated by containers are critical for deployments because they provide insights into the 
  health of the system.  PostgreSQL logs are very detailed and there is some information that can only be 
  obtained from logs (but not limited to):
  
  * Connections and Disconnections of users
  * Checkpoint Statistics
  * PostgreSQL Server Errors
  
  Aggregrating container logs across multiple hosts allows administrators to audit, debug problems and prevent 
  repudiation of misconduct.
  
  In the following example we will demonstrate how to setup Kubernetes and OpenShift to use centralized logging by using 
  an EFK (Elasticsearch, Fluentd and Kibana) stack.  Fluentd will run as a daemonset on each host within the Kubernetes 
  cluster and extract container logs, Elasticsearch will consume and index the logs gathered by Fluentd and Kibana will allow 
  users to explore and visualize the logs via a web dashboard.
  
  To learn more about the EFK stack, see the following:
  
negative.code: ....
  # Kubernetes
  cd $CCPROOT/examples/kube/scheduler
  ./add-schedules.sh
  ....
  
  The scheduled tasks will (these are just for fast results, not recommended for production):
  