diff --git a/src/cloud/architecture/scaled-architecture.md b/src/cloud/architecture/scaled-architecture.md index 700da0151e3..16cbbc46a45 100644 --- a/src/cloud/architecture/scaled-architecture.md +++ b/src/cloud/architecture/scaled-architecture.md @@ -100,7 +100,7 @@ project-id@server-id:~$ The log locations vary slightly depending on the node. For example, a database log, such as the **MySQL error log**, is available on a core node (`/var/log/mysql/mysql-error.log`), but it is not available on a web node. -Each Pro plan account includes the [New Relic Logs service][nri], which automatically connects with log data from the application to provide dynamic log management. Aggregated log data from all nodes displays in the New Relic Logs UI so you can troubleshoot performance issues on specific nodes from a single dashboard. +Each Pro plan account includes the [New Relic Logs service][nri], which automatically connects with log data from the application to provide dynamic log management. Aggregated log data from all nodes displays in the New Relic Logs application so that you can troubleshoot performance issues on specific nodes from a single dashboard. [Core tier scaling]: {{ site.baseurl }}/common/images/cloud/scaling-core.png diff --git a/src/cloud/project/log-locations.md b/src/cloud/project/log-locations.md index 0fac1e11800..98bdb1de957 100644 --- a/src/cloud/project/log-locations.md +++ b/src/cloud/project/log-locations.md @@ -1,33 +1,28 @@ --- group: cloud-guide -title: View logs +title: View and manage logs functional_areas: - Cloud - Configuration redirect_from: - /cloud/trouble/environments-logs.html --- -Logs are useful for troubleshooting problems related to {{site.data.var.ece}} [build and deploy hooks][hook]. - {:.bs-callout-info} -Magento-specific logs are in the `/var/` directory. See [Magento Logging][configlog] in the _Configuration guide_. +Logs for {{site.data.var.ece}} projects are useful for troubleshooting problems related to {{site.data.var.ece}} [build and deploy hooks][hook], cloud services, and the Magento application. -{:.bs-callout-tip} -When you configure your Cloud environment, you can [set up log-based Slack and email notifications][slacklog] for build and deploy actions. - -## Viewing logs - -There are three ways to view logs: file system, project web UI, `magento-cloud` CLI. +You can view the logs from the file system, the project web UI, and the `magento-cloud` CLI. -- **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. In Pro Production and Staging environments, you must check the logs on each node. +- **File system**—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. In Pro Production and Staging environments, you must check the logs on each node. - **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. -### Aggregated log data +## Manage log data -On Pro Production and Staging environments, you can review and analyze aggregated data from all {{ site.data.var.ece }} logs using the New Relic Logs service. See [New Relic services][]. +On Pro Production and Staging environments, use the New Relic Logs application integrated with your project to manage aggregated log data from all logs associated with your {{ site.data.var.ece }} project. + +The New Relic Logs application provides a centralized log management dashboard to troubleshoot and monitor {{site.data.var.ece}} Production and Staging environments. The dashboard also provides access to log data for Fastly CDN, Image Optimization, and Web application firewall (WAF) services. See [New Relic services][]. ### Log command @@ -78,6 +73,9 @@ Re-deploying environment project-integration-ID [2019-01-03 19:44:32] NOTICE: Post-deploy is complete. ``` +{:.bs-callout-tip} +When you configure your Cloud environment, you can set up [log-based Slack and email notifications][slacklog] for build and deploy actions. + ### Error logs Error and warning messages generated during the deployment process are written to both the `var/log/cloud.log` and the `var/log/cloud.error.log` files. The Cloud error log file contains only errors and warnings from the latest deployment. An empty file indicates a successful deployment with no errors. diff --git a/src/cloud/project/new-relic.md b/src/cloud/project/new-relic.md index 9ed387ec242..7ddaa37ab3c 100644 --- a/src/cloud/project/new-relic.md +++ b/src/cloud/project/new-relic.md @@ -46,7 +46,7 @@ The aggregated data includes information from the following logs: As soon as your project is connected to New Relic, you can use the New Relic Logs service to complete tasks like the following: - Use [New Relic queries][New Relic query syntax for logs] to search aggregated log data -- Visualize log data through the New Relic UI +- Visualize log data through the New Relic Logs application - Create custom charts, dashboards, and alerts - Troubleshoot performance issues from a single dashboard @@ -221,7 +221,10 @@ To use the New Relic Logs application: 1. On the _APM applications page_, select **Logs** from the navigation menu. - ![Cloud project APM menu select Logs page]({{ site.baseurl }}/common/images/cloud/cloud-newrelic-dashboard-basic.png){:width="650px"} + ![Cloud project APM menu select Logs page]({{ site.baseurl }}/common/images/cloud/cloud-newrelic-dashboard-logs-access.png){:width="650px"} + + {:.bs-callout-tip} + You can also access the New Relic Logs application from the New Relic ONE home page. See [New Relic ONE core UI components][New Relic One UI]. 1. To review infrastructure log data for cloud services, enter the query string `has: "ident"` in the _Find logs where_ field. Then, click **Query logs**. @@ -351,6 +354,7 @@ See [Alerts concepts and workflow] in the New Relic documentation for more detai [New Relic account]: #manage-your-new-relic-account [New Relic APM]: https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-new-relic-apm [New Relic APM Overview]: https://docs.newrelic.com/docs/apm/applications-menu/monitoring/apm-overview-page-view-transaction-apdex-usage-data +[New Relic ONE UI]: https://docs.newrelic.com/docs/new-relic-one/use-new-relic-one/get-started/new-relic-one-core-ui-components [New Relic for application performance management (APM)]: https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-new-relic-apm [New Relic Help Center]: https://newrelic.com/ [New Relic Logs]: https://docs.newrelic.com/docs/logs/new-relic-logs/get-started/introduction-new-relic-logs diff --git a/src/common/images/cloud/cloud-newrelic-dashboard-logs-access.png b/src/common/images/cloud/cloud-newrelic-dashboard-logs-access.png new file mode 100644 index 00000000000..5e980fb5026 Binary files /dev/null and b/src/common/images/cloud/cloud-newrelic-dashboard-logs-access.png differ