Skip to content

Commit 2f13019

Browse files
author
dksimpson
committed
task 444: edit procedures
1 parent bda7d0a commit 2f13019

File tree

1 file changed

+9
-10
lines changed

1 file changed

+9
-10
lines changed

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

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -20,17 +20,13 @@ ms.author: v-deasim
2020

2121
# Azure diagnostic logs
2222

23-
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).
24-
25-
With this feature, you can view core analytics and save them into one or more destinations including:
23+
With Azure diagnostic logs, you can view core analytics and save them into one or more destinations including:
2624

2725
- Azure Storage account
2826
- Azure Event Hubs
2927
- [OMS Log Analytics repository](https://docs.microsoft.com/azure/log-analytics/log-analytics-get-started)
3028

31-
This feature is available for all CDN endpoints belonging to Verizon (Standard and Premium) and Akamai (Standard) CDN Profiles.
32-
33-
For more information about diagnostic logs, see [Diagnostic Logs](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitoring-overview-of-diagnostic-logs).
29+
This feature is available for all CDN endpoints belonging to Verizon (Standard and Premium) and Akamai (Standard) CDN Profiles.
3430

3531
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:
3632

@@ -44,6 +40,7 @@ The following figure shows a typical CDN core analytics view of data.
4440

4541
*Figure 1 - CDN core analytics view*
4642

43+
For more information about diagnostic logs, see [Diagnostic Logs](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitoring-overview-of-diagnostic-logs).
4744

4845
## Enable logging with Azure portal
4946

@@ -62,7 +59,8 @@ Sign in to the [Azure portal](http://portal.azure.com). If you don't already hav
6259

6360
### Enable logging with Azure Storage
6461

65-
To use Azure Storage to store the logs, select **Archive to a storage account**, **CoreAnalytics**, and choose the number of retention days under **Retention (days)**.
62+
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.
63+
2. Enter a name for your setting, then click **Storage account**. After you have selected a storage account, click **Save**.
6664

6765
![portal - Diagnostics logs](./media/cdn-diagnostics-log/04_Diagnostics-logs-storage.png)
6866

@@ -76,15 +74,16 @@ To use OMS Log Analytics to store the logs, follow these steps:
7674

7775
![portal - Diagnostics logs](./media/cdn-diagnostics-log/05_Ready-to-Configure.png)
7876

79-
2. Click **Configure** to configure log analytics logging. In the resulting dialog box, you can select a previous workspace or create a new one.
77+
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.
8078

8179
![portal - Diagnostics logs](./media/cdn-diagnostics-log/06_Choose-workspace.png)
8280

8381
3. Click **Create New Workspace**.
8482

8583
![portal - Diagnostics logs](./media/cdn-diagnostics-log/07_Create-new.png)
8684

87-
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. 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.
85+
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.
86+
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.
8887

8988
![portal - Diagnostics logs](./media/cdn-diagnostics-log/08_Workspace-resource.png)
9089

@@ -132,7 +131,7 @@ To Enable Diagnostics Logs in an OMS workspace, use this command:
132131

133132

134133
## Consuming diagnostics logs from Azure Storage
135-
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 into a CSV file.
134+
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.
136135

137136
### Using Microsoft Azure Storage Explorer
138137
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.

0 commit comments

Comments
 (0)