Merge branch 'master' into small-changes

Author: dobooth

guides/v2.2/cloud/project/log-locations.md

@@ -18,10 +18,10 @@ You can [set up log-based Slack and email notifications][slacklog] when configur
 
 ## Viewing logs
 
-There are three ways to view logs: file system, project web UI, or magento-cloud CLI.
+There are three ways to view logs: file system, project web UI, or the `magento-cloud` CLI.
 
--  **Log directories**—The `var/log` directory contains logs for all environments. You must use an SSH connection to access the `var/log` directory in the remote server environment.
--  **Project web UI**—You can see build and post-deploy log information in the environment messages list.
+-  **Log directories**—The `/var/log` system directory contains logs for all environments. The `var/log/` Magento directory contains app-specific logs unique to a particular environment. You must use an SSH connection to access logs in a remote server environment. These directories are not shared between nodes in a cluster.
+-  **Project web UI**—You can see build and post-deploy log information in the environment _messages_ list.
 -  **Magento Cloud CLI**—You can view logs using the `magento-cloud log` command.
 
 ### Log command
@@ -45,7 +45,6 @@ Enter a number to choose a log:
   [6] post-deploy
  >
 ```
-{:.no-copy}
 
 By default, the command displays the log from the Integration environment. For the Pro Staging logs, you need to specify the log location using the project ID.
 
@@ -73,23 +72,22 @@ Re-deploying environment project-integration-ID
     [2019-01-03 19:44:32] INFO: Warming up failed: http://integration-id-project.us.magentosite.cloud/
     [2019-01-03 19:44:32] NOTICE: Post-deploy is complete.
 ```
-{: .no-copy}
 
 The following logs have a common location for all Cloud projects:
 
 -  **Build log**: `var/log/cloud.log`
 -  **Debug log**: `var/log/debug.log`
 -  **Exception log**: `var/log/exception.log`
--  **Support report log**: `var/log/support_report.log`
+-  **Reports**: `var/reports/`
 
-Logs from the deploy hook are unique for each environment. The deploy log is in the following directories:
+Though the `cloud.log` file contains feedback from each stage of the deployment process, logs from the deploy hook are unique to each environment. The environment-specific deploy log is in the following directories:
 
--  **Starter and Pro Integration**: `var/log/deploy.log`
--  **Pro Staging**: `var/log/platform/<project_id>_stg/deploy.log`
--  **Pro Production**: `var/log/platform/<project_id>/deploy.log`
+-  **Starter and Pro Integration**: `/var/log/deploy.log`
+-  **Pro Staging**: `/var/log/platform/<project_id>_stg/deploy.log`
+-  **Pro Production**: `/var/log/platform/<project_id>/deploy.log`
 
 The value of `<project_id>` depends on the project ID and whether the environment is Staging or Production. For example, with a project ID of `yw1unoukjcawe`, the Staging environment user is `yw1unoukjcawe_stg` and the Production environment user is `yw1unoukjcawe`.
-Using that example, the deploy log is: `var/log/platform/yw1unoukjcawe_stg/deploy.log`
+Using that example, the deploy log is: `/var/log/platform/yw1unoukjcawe_stg/deploy.log`
 
 The log for each deployment concatenates to the specific `deploy.log` file. The following example prints the deploy log in the terminal:
 
@@ -119,28 +117,31 @@ magento-cloud log platform/<project_id>_stg/deploy
 
 ## Application logs
 
-Similar to deploy logs, application logs are unique for each environment. The following table lists application log locations on each environment:
+Similar to deploy logs, application logs are unique for each environment. For Pro Staging and Production environments, the Deploy, Post-deploy, and Cron logs are available only on the first node in the cluster.
+
+The following table lists application log locations on each environment:
 
 Log file            | Starter and Pro Integration | Pro Staging                                       | Pro Production
 ------------------- | --------------------------- | ------------------------------------------------- | -------------------------------------------
-**Deploy log**      | `var/log/deploy.log`       | `var/log/platform/<project_id>_stg/deploy.log`   | `/var/log/platform/<project_id>/deploy.log`
-**Cron log**        | `var/log/cron.log`         | `var/log/platform/<project_id>_stg/cron.log`     | `var/log/platform/<project_id>/cron.log`
-**Nginx access log**| `var/log/access.log`       | `var/log/platform/<project_id>_stg/access.log`   | `/var/log/platform/<project_id>/access.log`
-**Nginx error log** | `var/log/error.log`        | `var/log/platform/<project_id>_stg/error.log`    | `/var/log/platform/<project_id>/error.log`
-**PHP access log**  | `var/log/php.access.log`   | `var/log/platform/<project_id>_stg/php.access.log` | `/var/log/platform/<project_id>/php.access.log`
-**PHP FPM log**     | `var/log/app.log`          | `var/log/platform/<project_id>_stg/php5-fpm.log` | `var/log/platform/<project_id>/php5-fpm.log`
+**Deploy log**      | `/var/log/deploy.log`       | First node only:<br>`/var/log/platform/<project_id>_stg/deploy.log`   | First node only:<br>`/var/log/platform/<project_id>/deploy.log`
+**Post-deploy log**      | `/var/log/post_deploy.log`       | First node only:<br>`/var/log/platform/<project_id>_stg/post_deploy.log`   | First node only:<br>`/var/log/platform/<project_id>/post_deploy.log`
+**Cron log**        | `/var/log/cron.log`         | First node only:<br>`/var/log/platform/<project_id>_stg/cron.log`     | First node only:<br>`/var/log/platform/<project_id>/cron.log`
+**Nginx access log**| `/var/log/access.log`       | `/var/log/platform/<project_id>_stg/access.log`   | `/var/log/platform/<project_id>/access.log`
+**Nginx error log** | `/var/log/error.log`        | `/var/log/platform/<project_id>_stg/error.log`    | `/var/log/platform/<project_id>/error.log`
+**PHP access log**  | `/var/log/php.access.log`   | `/var/log/platform/<project_id>_stg/php.access.log` | `/var/log/platform/<project_id>/php.access.log`
+**PHP FPM log**     | `/var/log/app.log`          | `/var/log/platform/<project_id>_stg/php5-fpm.log` | `/var/log/platform/<project_id>/php5-fpm.log`
 
 ## Service logs
 
 Because each service runs in a separate container, the service logs are not available in the Integration environment. {{site.data.var.ece}} provides access to the web server container in the Integration environment only. The following service log locations are for the Pro Staging and Production environments:
 
--  **Redis log**: `var/log/platform/<project_id>_stg/redis-server-<project_id>_stg.log`
--  **Elasticseach log**: `var/log/elasticsearch/elasticsearch.log`
--  **Mail log**: `var/log/mail.log`
--  **MySQL error log**: `var/log/mysql/mysql-error.log`
--  **MySQL slow log**: `var/log/mysql/mysql-slow.log`
--  **RabbitMQ log**: `var/log/rabbitmq/[email protected]`
+-  **Redis log**: `/var/log/platform/<project_id>_stg/redis-server-<project_id>_stg.log`
+-  **Elasticseach log**: `/var/log/elasticsearch/elasticsearch.log`
+-  **Mail log**: `/var/log/mail.log`
+-  **MySQL error log**: `/var/log/mysql/mysql-error.log`
+-  **MySQL slow log**: `/var/log/mysql/mysql-slow.log`
+-  **RabbitMQ log**: `/var/log/rabbitmq/[email protected]`
 
 [hook]: {{page.baseurl}}/cloud/project/project-conf-files_magento-app.html#hooks
 [configlog]: {{page.baseurl}}/config-guide/cli/logging.html
-[slacklog]: {{page.baseurl}}/cloud/env/setup-notifications.html
+[slacklog]: {{page.baseurl}}/cloud/env/setup-notifications.html