Skip to content

Latest commit

 

History

History
36 lines (25 loc) · 2.02 KB

cdn-log-analysis.md

File metadata and controls

36 lines (25 loc) · 2.02 KB
title description services documentationcenter author manager editor ms.assetid ms.service ms.workload ms.tgt_pltfrm ms.devlang ms.topic ms.date ms.author
Analyze Azure CDN usage patterns | Microsoft Docs
Customer can enable log analysis for Azure CDN.
cdn
smcevoy
erikre
95e18b3c-b987-46c2-baa8-a27a029e3076
cdn
tbd
na
na
article
08/03/2017
v-semcev

Analyze Azure CDN usage patterns

After you enable CDN for your application, you can monitor CDN usage, check the health of your delivery, and troubleshoot potential issues. Azure CDN provides these capabilities in the following two ways:

Verizon Core Reports

As an Azure CDN user with a Verizon standard or a Verizon premium profile, you can view Verizon Core Reports in the Verizon supplemental portal. Verizon Core Reports is accessible via the Manage option from the Azure portal and offers a variety of graphs and views. For more information, see Core Reports from Verizon.

Verizon Custom Reports

As an Azure CDN user with a Verizon standard or a Verizon premium profile, you can view Verizon Custom Reports in the Verizon supplemental portal. Verizon Custom Reports is accessible via the Manage option from the Azure portal. The Verizon Custom Reports page shows the number of hits or data transferred for each edge CName belonging to an Azure CDN profile. The data can be grouped by HTTP response code or cache status over any period of time. For more information, see Custom Reports from Verizon.

Core analytics via Azure diagnostic logs

Core analytics is available for all CDN endpoints belonging to Verizon (Standard and Premium) and Akamai (Standard) CDN profiles. Azure diagnostics logs allow core analytics to be exported to Azure storage, event hubs, or Operations Management Suite (OMS) Log Analytics. OMS Log Analytics offers a solution with graphs that are user-configurable and customizable. For more information, see Azure diagnostic logs.