Merge pull request #5457 from newrelic/DOC-7604-logs-UI

feat(Logs everywhere): Screenshots 12-30-21

src/content/docs/logs/forward-logs/enable-log-management-new-relic.mdx

@@ -40,6 +40,14 @@ When you configure your log forwarder (our infrastructure monitoring agent, Flue
 
 Now your log files are enriched with enhanced metadata and contextual logging data. Your log forwarder sends the files to our logging endpoint for processing. From there you can use our log management capabilities to view, query, set up alerts, and more in New Relic.
 
+Here is an example of logs for your host's UI. You can see logs in context of events for the selected time period, and drill down into detailed data for any of the highlighted attributes. To take advantage of even more capabilities, click **Query logs** from here to go directly to the **Logs** UI.
+
+![Logs in context for a host](./images/demotron-host-logs-123021.png "Logs in context for a host")
+
+<figcaption>
+  Here is an example of a host's logs in context related to an event.
+</figcaption>
+
 ## Get started with log forwarders [#compatibility-requirements]
 
 To forward your logs to New Relic with enriched metadata:

src/content/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent.mdx

@@ -44,10 +44,12 @@ To forward your logs through our infrastructure monitoring agent:
 6. Generate some traffic and wait a few minutes, then [check your account](#find-data) for data.
 7. [Explore your log data](#what-next) in the Logs UI and benefit from the log attributes automatically inserted by the infrastructure agent.
 
-![Logs in context of infrastructure monitoring UI](./images/infrastructure-lic.png "Logs in context of infrastructure monitoring UI")
+Here is an example of logs for your host's UI. You can see logs in context of events for the selected time period, and drill down into detailed data for any of the highlighted attributes. To take advantage of even more capabilities, click **Query logs** from here to go directly to the **Logs** UI.
+
+![Logs in context for a host](./images/demotron-host-logs-123021.png "Logs in context for a host")
 
 <figcaption>
-  Here is an example of where you can see logs in context of your infrastructure monitoring details in New Relic One.
+  Here is an example of a host's logs in context related to an event.
 </figcaption>
 
 ## System requirements [#requirements]
@@ -952,17 +954,17 @@ If you encounter problems with configuring your log forwarder, try these trouble
 
 </CollapserGroup>
 
-## Uninstall log forwarding [#uninstall]
-
-To uninstall log forwarding capabilities, go to your `logging.d` directory, and remove files with the `.yml` extension that were originally added during the [configuration](#configure) process.
-
-* Linux: `/etc/newrelic-infra/logging.d/`
-* Windows: `C:\Program Files\New Relic\newrelic-infra\logging.d\`
-
 ## What's next? [#what-next]
 
 Explore logging data across your platform with the [New Relic One UI](/docs/logs/log-management/ui-data/use-logs-ui/).
 
 * Get deeper visibility into both your application and your platform performance data by forwarding your logs with our [logs in context](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-apm-agents/) capabilities.
 * Set up [alerts](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions/).
 * [Query your data](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/) and [create dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/).
+
+## Uninstall log forwarding [#uninstall]
+
+To uninstall log forwarding capabilities, go to your `logging.d` directory, and remove files with the `.yml` extension that were originally added during the [configuration](#configure) process.
+
+* Linux: `/etc/newrelic-infra/logging.d/`
+* Windows: `C:\Program Files\New Relic\newrelic-infra\logging.d\`

src/content/docs/logs/get-started/get-started-log-management.mdx

@@ -66,6 +66,16 @@ SELECT * FROM Log
 
 You can also use NerdGraph, our GraphQL-format API, to request the exact data you need.
 
+Here is an example of log data for one of an app's related entities (a workload service in this example):
+
+![Log data for an app's related service](./images/demotron-services-logs-123021c.png "Log data for an app's related service")
+
+You can also see relevant logs in context, directly from the app in the APM UI or from the host in the Hosts UI in New Relic One.
+
+![Log data link from APM UI](./images/demotron-logs-123021.png "Log data link from APM UI")
+
+From here you can drill down into detailed data, run queries, set alerts, and more.
+
 ## What's next [#what-next]
 
 Ready to get started with our log management solutions?

src/content/docs/logs/logs-context/configure-logs-context-apm-agents.mdx

@@ -45,6 +45,10 @@ Don't spend extra time trying to narrow down all your logs from different parts
 
 ## Basic process to enable logs in context [#enable-logs]
 
+Here is an example of logs for your app's UI. You can see logs in context of events for the selected time period, and drill down into detailed data for any of the highlighted attributes. To take advantage of even more capabilities, click **Query logs** from here to go directly to the **Logs** UI.
+
+![Logs in context in APM UI](./images/demotron-logs-123021.png "Logs in context in APM UI")
+
 The process to enable logs in context is basically the same, regardless of which APM agent you use to monitor your application:
 
 1. Make sure you have already [set up logging in New Relic](/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/enable-log-management-new-relic/). This includes configuring a supported log forwarder that collects your application logs and extends the metadata that is forwarded to New Relic.
@@ -76,16 +80,14 @@ If our logging solutions don't meet your needs, you can use other options to sen
 
 ## What's next? [#what-next]
 
-![Logs in context of trace details in APM UI](./images/logs-in-context-traces.png "Logs in context for trace details in APM UI")
-
-<figcaption>
-  Here is an example of logs in context for app trace details, visible in the APM UI.
-</figcaption>
-
 After you set up logs in context for APM or infrastructuring monitoring, make the most of your logging data in the New Relic One UI:
 
 * Explore the logging data across your platform with our [Logs UI](/docs/logs/log-management/ui-data/use-logs-ui/).
 * See your logs in context of your app's performance in the [APM UI](/docs/logs/log-management/ui-data/use-logs-ui/#links). Troubleshoot [errors](/docs/apm/apm-ui-pages/error-analytics/errors-page-find-fix-verify-problems/) with [distributed tracing](/docs/apm/distributed-tracing/ui-data/understand-use-distributed-tracing-data), stack traces, application logs, and more.
 * Get deeper visibility into both your application and your platform performance data by forwarding your logs with our [infrastructure monitoring agent](/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/forward-your-logs-using-infrastructure-agent/). Review your [infrastructure logs](/docs/logs/log-management/ui-data/use-logs-ui/#links) in the UI.
 * Set up [alerts](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions/).
 * [Query your data](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/) and [create dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/).
+
+Here is an example of logs in context for app trace details, visible from the APM UI.
+
+![Logs in context of trace details in APM UI](./images/logs-in-context-traces.png "Logs in context for trace details in APM UI")

src/content/docs/logs/ui-data/use-logs-ui.mdx

@@ -28,11 +28,9 @@ To stay up to date with new capabilities and improvements, subscribe to our [RSS
 
 ## Explore your log data [#ui-workflow]
 
-![Logs UI in New Relic One](./images/logs-ui-042721-summary.png "Logs UI in New Relic One")
+Use the left nav in the Logs UI as an easy workflow through all logs, attributes, patterns, live-tail logging, and queries. Manage your log data by dropping or parsing data, creating data partitions or alert conditions. Get more details about specific logs and their attributes from the center nav.
 
-<figcaption>
-  Use the left nav in the Logs UI as an easy workflow through all logs, patterns, live-tail logging, and queries. Get more details about specific logs and their attributes from the center nav.
-</figcaption>
+![Logs UI in New Relic One](./images/logs-ui-123021.png "Logs UI in New Relic One")
 
 To explore your logging data, follow this basic workflow.
 
@@ -66,7 +64,7 @@ To explore your logging data, follow this basic workflow.
    service_name equals <var>my service</var>
    ```
 
-   For more information, see the [Logs query syntax documentation](/docs/logs/ui-data/query-syntax-logs/).
+   For more information, see the [logs query syntax documentation](/docs/logs/ui-data/query-syntax-logs/).
 
 <Callout variant="tip">
   To organize data within an account and to optimize query performance, create [data partition rules](/docs/logs/ui-data/data-partitions/).
@@ -157,7 +155,7 @@ Here are a few examples of how you can use the Logs UI to get detailed informati
 
 ## Links to logs in New Relic [#links]
 
-Depending on your New Relic subscription, you can access your logs from several places in the New Relic UI. For some of these options, you must be able to see [logs in context](/docs/enable-logs-context-logs).
+Depending on your New Relic subscription, you can access your logs from several places in the New Relic UI. For some of these options, you must be able to see [logs in context](/docs/logs/logs-context/configure-logs-context-apm-agents/).
 
 <table>
   <thead>
@@ -226,7 +224,7 @@ Depending on your New Relic subscription, you can access your logs from several
 
     <tr>
       <td>
-        From your app in APM [(logs in context)](/docs/enable-logs-context-logs)
+        From your app in APM [(logs in context)](/docs/logs/logs-context/configure-logs-context-apm-agents/)
       </td>
 
       <td>
@@ -236,7 +234,7 @@ Depending on your New Relic subscription, you can access your logs from several
 
     <tr>
       <td>
-        From an error trace in APM [(logs in context)](/docs/enable-logs-context-logs)
+        From an error trace in APM [(logs in context)](/docs/logs/logs-context/configure-logs-context-apm-agents/)
       </td>
 
       <td>