anchor.diff:  
   === 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 
  +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 
  +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 
  +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:
  
positive.code: View the `pgBaseBackup` pods results after the backup completes:
  
  ....
  ${CCP_CLI?} logs <basebackup job name>
  ....
  
  View the `pgBackRest` backups via exec after the backup completes:
  
negative.code: * https://www.fluentd.org/architecture
  * https://www.elastic.co/products/kibana
  
  ==== Configure PostgreSQL for Centralized Logging
  
  By default, Crunchy PostgreSQL logs to files in the `/pgdata` directory.  In order to get the logs
  out of the container we need to configure PostgreSQL to log to `stdout`.
  
  The following settings should be configured in `postgresql.conf` to make PostgreSQL log to `stdout`:
  