Merge pull request #24785 from dksimpson/dean-444

task 444: update screen shots and procedures

Author: rjagiewich

articles/cdn/cdn-azure-diagnostic-logs.md

@@ -20,53 +20,47 @@ ms.author: v-deasim
 
 # Azure diagnostic logs
 
-Azure diagnostic logs is available for all CDN endpoints belonging to Verizon (Standard and Premium) and Akamai (Standard) CDN Profiles. For more information, see [Diagnostic Logs](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitoring-overview-of-diagnostic-logs).
-
-With this feature, you can view core analytics and save them into one or more destinations including:
+With Azure diagnostic logs, you can view core analytics and save them into one or more destinations including:
 
  - Azure Storage account
  - Azure Event Hubs
  - [OMS Log Analytics repository](https://docs.microsoft.com/azure/log-analytics/log-analytics-get-started)
 
-This feature is available for all CDN endpoints belonging to Verizon (Standard and Premium) and Akamai (Standard) CDN Profiles.
-
-For more information about diagnostic logs, see [Diagnostic Logs](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitoring-overview-of-diagnostic-logs).
+This feature is available for all CDN endpoints belonging to Verizon (Standard and Premium) and Akamai (Standard) CDN Profiles. 
 
 Azure diagnostics logs allow you to export basic usage metrics from your CDN endpoint to a variety of sources so that you can consume them in a customized way. For example, you can do the following types of data export:
 
 - Export data to blob storage, export to CSV, and generate graphs in Excel.
 - Export data to Event Hubs and correlate with data from other Azure services.
 - Export data to log analytics and view data in your own OMS work space
 
-The following figure shows a typical CDN core analytics view into data.
+The following figure shows a typical CDN core analytics view of data.
 
 ![portal - Diagnostics logs](./media/cdn-diagnostics-log/01_OMS-workspace.png)
 
 *Figure 1 - CDN core analytics view*
 
-The following walkthrough goes through the schema of the core analytics data, steps involved in enabling the feature and delivering them to various destinations, and consuming from these destinations.
+For more information about diagnostic logs, see [Diagnostic Logs](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitoring-overview-of-diagnostic-logs).
 
 ## Enable logging with Azure portal
 
-> [!NOTE]
-> The diagnostics logs are turned **off** by default. 
-
-Follow the steps below to enable logging with CDN core analytics:
+Follow these steps enable logging with CDN core analytics:
 
 Sign in to the [Azure portal](http://portal.azure.com). If you don't already have CDN enabled for your workflow, [Enable Azure CDN](cdn-create-new-endpoint.md) before you continue.
 
 1. In the portal, navigate to **CDN profile**.
-2. Select a CDN profile, then select the CDN endpoint that you want to enable **Diagnostics Logs**.
+2. Select a CDN profile, then select the CDN endpoint for which you want to enable **Diagnostics Logs**.
 
 	![portal - Diagnostics logs](./media/cdn-diagnostics-log/02_Browse-to-Diagnostics-logs.png)
 
-3. Go to **Diagnostics Logs** blade Under **Monitoring** section, then change the status to **On**.
+3. Select **Diagnostics Logs** in the **Monitoring** section.
 
 	![portal - Diagnostics logs](./media/cdn-diagnostics-log/03_Diagnostics-logs-options.png)
 
 ### Enable logging with Azure Storage
 
-To use Azure Storage to store the logs, select **Archive to a storage account**, select retention days, and click **CoreAnalytics** under **Log**.
+1. To use Azure storage to store the logs, select **Archive to a storage account**, select **CoreAnalytics**, and then choose the number of retention days under **Retention (days)**. A retention of zero days stores the logs indefinitely. 
+2. Enter a name for your setting, then click **Storage account**. After you have selected a storage account, click **Save**.
 
 ![portal - Diagnostics logs](./media/cdn-diagnostics-log/04_Diagnostics-logs-storage.png)
 
@@ -76,37 +70,32 @@ To use Azure Storage to store the logs, select **Archive to a storage account**,
 
 To use OMS Log Analytics to store the logs, follow these steps:
 
-1. From the **Diagnostics Logs** blade Under **Monitoring**, select **Send to Log Analytics** from 
+1. From the **Diagnostics Logs** blade, select **Send to Log Analytics**. 
 
     ![portal - Diagnostics logs](./media/cdn-diagnostics-log/05_Ready-to-Configure.png)    
 
-2. Configure the Log Analytics logging by clicking on Configure. This takes you to a dialog where you can select a previous workspace or create a new one.
+2. Click **Configure** to configure log analytics logging. In the OMS Workspaces dialog box, you can select a previous workspace or create a new one.
 
     ![portal - Diagnostics logs](./media/cdn-diagnostics-log/06_Choose-workspace.png)
 
 3. Click **Create New Workspace**.
 
     ![portal - Diagnostics logs](./media/cdn-diagnostics-log/07_Create-new.png)
 
-4. Next you must select a new workspace name, existing subscription, resource group (new or existing), location, and pricing tier. You have the option of pinning this configuration to your dashboard. Click OK to complete the configuration.
-
-    Next you should see your workspace with your OMS Workspace and Resource group names. Names must be unique and can only use letters, numbers, and hyphens. Spaces and underscores are not allowed. 
+4. Enter a new OMS workspace name. An OMS workspace name must be unique and contain only letters, numbers, and hyphens; spaces and underscores are not allowed. 
+5. Next, select an existing subscription, resource group (new or existing), location, and pricing tier. You also have the option of pinning this configuration to your dashboard. Click **OK** to complete the configuration.
 
     ![portal - Diagnostics logs](./media/cdn-diagnostics-log/08_Workspace-resource.png)
 
-5. You next get a short message saying that your workspace has been created and you are returned to your logging configuration screen. You can confirm the name of your Log Analytics workspace.
+5.  After your workspace is created, you are returned to your Diagnostic logs windows. Confirm the name of your new log analytics workspace.
 
     ![portal - Diagnostics logs](./media/cdn-diagnostics-log/09_Return-to-logging.png)
 
-    Once you have set up the Log Analytics configuration, make sure you also check the CoreAnalytics box for CDN logging.
-
-6. If everything is to your liking, click the **Save** button at the top of the configuration dialog.
-
-    ![portal - Diagnostics logs](./media/cdn-diagnostics-log/10_Save-me.png)
+    Once you have set up the log analytics configuration, verify that you have selected  **CoreAnalytics**.
 
-    The **Save** button is no longer active and that the ON/OFF button is now ON, but blue instead of purple.
+6. Click **Save**.
 
-7. If you want to see your new OMS workspace, go to your Azure portal Dashboard, click the name of your Log Analytics workspace. Next you will see your workspace (make sure that OMS Workspace is highlighted on the left). Click on the OMS Portal tile to see your workspace in the OMS repository. 
+7. To view your new OMS workspace, go to your Azure portal dashboard and click the name of your log analytics workspace. Click the OMS Portal tile to view your workspace in the OMS repository. 
 
     ![portal - Diagnostics logs](./media/cdn-diagnostics-log/11_OMS-dashboard.png) 
 
@@ -116,7 +105,7 @@ For more information about log data delays, see [Log data delays](#log-data-dela
 
 ## Enable logging with PowerShell
 
-Below is an example on how to enable and get Diagnostic Logs via the Azure PowerShell Cmdlets.
+The following example shows how to enable Diagnostic Logs via the Azure PowerShell Cmdlets.
 
 ###Enabling Diagnostic Logs in a Storage Account
 
@@ -142,10 +131,10 @@ To Enable Diagnostics Logs in an OMS workspace, use this command:
 
 
 ## Consuming diagnostics logs from Azure Storage
-This section describes the schema of the CDN core analytics, how these are organized inside of an Azure Storage Account and provides sample code to download the logs into a CSV file.
+This section describes the schema of CDN core analytics, how it is organized inside of an Azure storage account, and provides sample code to download the logs in a CSV file.
 
 ### Using Microsoft Azure Storage Explorer
-Before you can access the core analytics data from the Azure Storage Account, you first need a tool to access the contents in a storage account. While there are several tools available in the market, the one that we recommend is the Microsoft Azure Storage Explorer. You can download the tool from [here](http://storageexplorer.com/). After downloading and installing the software, configure it to use the same Azure Storage Account that was configured as a destination to the CDN Diagnostics Logs.
+Before you can access the core analytics data from the Azure Storage Account, you first need a tool to access the contents in a storage account. While there are several tools available in the market, the one that we recommend is the Microsoft Azure Storage Explorer. To download the tool, see [Azure Storage Explorer](http://storageexplorer.com/). After downloading and installing the software, configure it to use the same Azure storage account that was configured as a destination to the CDN Diagnostics Logs.
 
 1.	Open **Microsoft Azure Storage Explorer**
 2.	Locate the storage account
@@ -159,34 +148,34 @@ Before you can access the core analytics data from the Azure Storage Account, yo
 > [!NOTE]
 > **Blob path format**
 > 
-> Core analytics logs are generated every hour. All data for an hour are collected and stored inside a single Azure Blob as a JSON payload. The path to this Azure Blob appears as if there is a hierarchical structure. This is because the Storage explorer tool interprets '/' as a directory separator and shows the hierarchy for convenience. Actually, the whole path just represents the blob name. This name of the blob follows the following naming convention	
+> Core analytics logs are generated every hour and the data is collected and stored inside a single Azure blob as a JSON payload. Because the Storage explorer tool interprets '/' as a directory separator and shows the hierarchy, the path to the Azure blob appears as if there is a hierarchical structure and represents the blob name. The name of the blob follows the following naming convention:	
 	
 	resourceId=/SUBSCRIPTIONS/{Subscription Id}/RESOURCEGROUPS/{Resource Group Name}/PROVIDERS/MICROSOFT.CDN/PROFILES/{Profile Name}/ENDPOINTS/{Endpoint Name}/ y={Year}/m={Month}/d={Day}/h={Hour}/m={Minutes}/PT1H.json
 
 **Description of fields:**
 
 |value|description|
 |-------|---------|
-|Subscription ID	|ID of the Azure Subscription. This is in the Guid format.|
+|Subscription ID	|ID of the Azure subscription in Guid format.|
 |Resource |Group Name	Name of the resource group to which the CDN resources belong.|
 |Profile Name |Name of the CDN Profile|
 |Endpoint Name |Name of the CDN Endpoint|
-|Year|	4-digit representation of the year for example, 2017|
+|Year|	4-digit representation of the year, for example, 2017|
 |Month|	2-digit representation of the month number. 01=January ... 12=December|
-|Day|	2 digit representation of the day of the month|
+|Day|	2-digit representation of the day of the month|
 |PT1H.json|	Actual JSON file where the analytics data is stored|
 
 ### Exporting the core analytics data to a CSV file
 
-To make it easy to access core analytics, we provide a sample code for a tool, which allows downloading the JSON files into a flat comma-separated file format, which can be used to easily create charts or other aggregations.
+To make it easy to access core analytics, sample code for a tool is provided. This tool allows downloading the JSON files into a flat comma-separated file format, which can be used to easily create charts or other aggregations.
 
 Here is how you can use the tool:
 
 1.	Visit the github link: [https://github.com/Azure-Samples/azure-cdn-samples/tree/master/CoreAnalytics-ExportToCsv ](https://github.com/Azure-Samples/azure-cdn-samples/tree/master/CoreAnalytics-ExportToCsv )
-2.	Download the code
-3.	Follow instructions to compile and configure
-4.	Run the tool
-5.	Resulting CSV file shows the analytics data in a simple flat hierarchy.
+2.	Download the code.
+3.	Follow the instructions to compile and configure.
+4.	Run the tool.
+5.	The resulting CSV file shows the analytics data in a simple flat hierarchy.
 
 ## Consuming diagnostics logs from an OMS Log Analytics repository
 Log Analytics is a service in Operations Management Suite (OMS) that monitors your cloud and on-premises environments to maintain their availability and performance. It collects data generated by resources in your cloud and on-premises environments and from other monitoring tools to provide analysis across multiple sources. 
@@ -244,7 +233,7 @@ Follow these steps to add a Management Solution:
 
     ![See all](./media/cdn-diagnostics-log/21_Ready.png)
 
-10. Your solution has now been added to your workspace. Go back to your Azure portal Dashboard.
+10. Your solution has now been added to your workspace. Return to your Azure portal dashboard.
 
     ![See all](./media/cdn-diagnostics-log/22_Dashboard.png)
 
@@ -274,11 +263,11 @@ You can see offers and pricing tiers for OMS management solutions [here](https:/
 
 ### Customizing views
 
-You can customize the view into your data by using the **View Designer**. Go to your OMS workspace and begin designing by clicking the **View Designer** tile.
+You can customize the view into your data by using the **View Designer**. To begin designing, go to your OMS workspace and click the **View Designer** tile.
 
 ![View Designer](./media/cdn-diagnostics-log/27_Designer.png)
 
-You can drag and drop types of charts from the left and fill in the data details you want to analyze on the left.
+You can drag and drop the types of charts and fill in the data details you want to analyze.
 
 ![View Designer](./media/cdn-diagnostics-log/28_Designer.png)
 
@@ -287,7 +276,7 @@ You can drag and drop types of charts from the left and fill in the data details
 
 Verizon log data delays | Akamai log data delays
 --- | ---
-Verizon log data is 1 hour delayed, and take up to 2 hours to start appearing after endpoint propagation completion. | Akamai log data is 24 hours delayed, and takes up to 2 hours to start appearing if it was created more than 24 hours ago. If it was recently created, it can take up to 25 hours for the logs to start appearing.
+Verizon log data is 1 hour delayed, and take up to 2 hours to start appearing after endpoint propagation completion. | Akamai log data is delayed by 24 hours; if it was created more than 24 hours ago, it takes up to 2 hours to start appearing. If it was recently created, it can take up to 25 hours for the logs to start appearing.
 
 ## Diagnostic log types for CDN core analytics
 
@@ -310,7 +299,7 @@ The following table shows a list of metrics available in the core analytics logs
 | RequestCountHttpStatus302 | Count of all requests that resulted in a 302 HTTP code response              |No   |Yes   |
 | RequestCountHttpStatus304 |  Count of all requests that resulted in a 304 HTTP code response             |No   |Yes   |
 | RequestCountHttpStatus404 | Count of all requests that resulted in a 404 HTTP code response              |No   |Yes   |
-| RequestCountCacheHit |Count of all requests that resulted in a Cache Hit. This means the asset was served directly from the POP to the Client.               | Yes  |No   |
+| RequestCountCacheHit |Count of all requests that resulted in a Cache Hit. The asset was served directly from the POP to the client.               | Yes  |No   |
 | RequestCountCacheMiss | Count of all requests that resulted in a Cache Miss. This means the asset was not found on the POP closest to the client, and therefore was retrieved from the Origin.              |Yes   | No  |
 | RequestCountCacheNoCache | Count of all requests to an asset that are prevented from being cached due to a user configuration on the edge.              |Yes   | No  |
 | RequestCountCacheUncacheable | Count of all requests to assets that are prevented from being cached by the asset's Cache-Control and Expires headers, which indicate that it should not be cached on a POP or by the HTTP client                |Yes   |No   |
@@ -324,15 +313,15 @@ The following table shows a list of metrics available in the core analytics logs
 | EgressCacheHit |  Outbound data transfer for responses that were delivered directly from the CDN cache on the CDN POPs/Edges	|Yes   |  No |
 | EgressCacheMiss | Outbound data transfer for responses that were not found on the nearest POP server, and retrieved from the origin server              |Yes   |  No |
 | EgressCacheNoCache | Outbound data transfer for assets that are prevented from being cached due to a user configuration on the edge.                |Yes   |No   |
-| EgressCacheUncacheable | Outbound data transfer for assets that are prevented from being cached by the asset's Cache-Control and/or Expires headers, which indicate that it should not be cached on a POP or by the HTTP client                    |Yes   | No  |
+| EgressCacheUncacheable | Outbound data transfer for assets that are prevented from being cached by the asset's Cache-Control and/or Expires headers. Indicates that it should not be cached on a POP or by the HTTP client.                   |Yes   | No  |
 | EgressCacheOthers |  Outbound data transfers for other cache scenarios.             |Yes   | No  |
 
 *Outbound data transfer refers to traffic delivered from CDN POP servers to the client.
 
 
 ### Schema of the core analytics logs 
 
-All logs are stored in JSON format and each entry has string fields following the below schema:
+All logs are stored in JSON format and each entry has string fields according to the following schema:
 
 ```json
     "records": [
@@ -377,9 +366,9 @@ All logs are stored in JSON format and each entry has string fields following th
 }
 ```
 
-Where the ‘time’ represents the start time of the hour boundary for which the statistics is reported. When a metric is not supported by a CDN provider, instead of a double or integer value, there will be a null value. This null value indicates the absence of a metric, and this is different from a 0 value. Also note that there will be one set of these metrics per domain configured on the endpoint.
+Where the ‘time’ represents the start time of the hour boundary for which the statistics is reported. When a metric is not supported by a CDN provider, instead of a double or integer value, there is a null value. This null value indicates the absence of a metric, and is different from a value of 0. There is one set of these metrics per domain configured on the endpoint.
 
-Example properties below:
+Example properties:
 
 ```json
 {