The following are recommended Cloud Foundry dashboards found in the files cf_summary,  cf_router, and cf_cell_summary, located at:  https://github.com/bosh-prometheus/prometheus-boshrelease/tree/master/jobs/cloudfo undry_dashboards/templates . A Cloud Foundry deployment can produce a lot of log output, both from the components that  make up the Cloud Foundry platform itself and the applications you run in the environment. Logs produced by Cloud Foundry components, which we see as syslogs, can be viewed  directly on the BOSH instances (for Cloud Foundry Full Stack) or the Kubernetes pods (for  Cloud Foundry Enterprise Environment). Most logs are output to a subdirectory  corresponding to the job name under the  /var/vcap/sys/log directory . Syslogs are subject to rotation to avoid using up all the storage available to the Cloud  Foundry components, so their lifespan is limited.  Logs from applications deployed in the environment, or applogs, can be accessed using the  Cloud Foundry CLI or any tooling that integrates with the Cloud Foundry firehose, such as the  Cloud Foundry management console. These logs are a real-time stream, with a limited  amount of history available. Cloud Foundry Full Stack provides extensions for log forwarding that allow you to forward logs  to a logging system of your choice for retention and analysis. An integration with the Elastic  Stack logging system in IBM Cloud Private is also provided. The cfp-ext-syslog-forwarder  and  cfp-ext-applog-forwarde r are embedded extensions  for the Cloud Foundry deployment tool that allow you to configure forwarding of syslogs and  applogs. When you add either extension, it is automatically inserted after the “Prepare Cloud  Foundry” state and before the “Deploy Cloud Foundry” state. You configure the extensions by  providing the details of where and how the logs should be forwarded. Then, when the deployment is run, the extensions insert the configuration values in the  required configuration files so that the “Deploy Cloud Foundr y” state will configure the Cloud  Foundry components to forward logs according to the configuration. For syslog forwarding, all  Cloud Foundry components are modified and individually forward their logs according the  configuration. For applog forwarding, the Doppler instances (typically 4), a core component of  the Cloud Foundry logging system, are modified to forward all application logs. Both  extensions can be configured automatically if you are using the integration with the Elastic  Stack provided in IBM Cloud Private. Integration with Elastic Stack in IBM Cloud Private is achieved by using a Helm chart that  Cloud Foundry Full Stack exports during the “Prepare Helm charts” state. After running this  state of the deployment, an archive file containing the ibm-cflogging Helm chart and required  images can be found in the IBMCloudPrivate subdirectory of the installation configuration  directory. The ibm-cflogging Helm chart provides a Logstash deployment that can be configured to  accept syslogs and applogs from the cfp-ext-syslog-forwarder and cfp-ext-applog-forwarder  extensions. This deployment of Logstash outputs logs to the Elasticsearch deployment  provided by IBM Cloud Private, which allows you to view, search, and visualize logs in  Kibana. By default, all connections are made securely using mutual TLS. Chapter 10. IBM Cloud Private Cloud Foundry and common systems administration tasks  341 10.9.2 Logging