title | description | services | documentationcenter | author | manager | editor | ms.assetid | ms.service | ms.devlang | ms.topic | ms.tgt_pltfrm | ms.workload | ms.date | ms.author |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Monitor the health of Azure CDN resources| Microsoft Docs |
Learn how to monitor the health of your Azure CDN resources using Azure Resource Health. |
cdn |
.net |
zhangmanling |
zhangmanling |
bf23bd89-35b2-4aca-ac7f-68ee02953f31 |
azure-cdn |
multiple |
how-to |
na |
integration |
01/23/2017 |
mazha |
Azure CDN Resource health is a subset of Azure resource health. You can use Azure resource health to monitor the health of CDN resources and receive actionable guidance to troubleshoot problems.
Important
Azure CDN resource health only currently accounts for the health of global CDN delivery and API capabilities. Azure CDN resource health does not verify individual CDN endpoints.
The signals that feed Azure CDN resource health may be up to 15 minutes delayed.
-
In the Azure portal, browse to your CDN profile.
-
Click the Settings button.
-
Under Support + troubleshooting, click Resource health.
Tip
You can also find CDN resources listed in the Resource health tile in the Help + support blade. You can quickly get to Help + support by clicking the circled ? in the upper right corner of the portal.
Statuses related to Azure CDN resource health can be found below.
Message | Recommended Action |
---|---|
You may have stopped, removed, or misconfigured one or more of your CDN endpoints | You may have stopped, removed, or misconfigured one or more of your CDN endpoints. |
We are sorry, the CDN management service is currently unavailable | Check back here for status updates; If your problem persists after the expected resolution time, contact support. |
We're sorry, your CDN endpoints may be impacted by ongoing issues with some of our CDN providers | Check back here for status updates; Use the Troubleshoot tool to learn how to test your origin and CDN endpoint; If your problem persists after the expected resolution time, contact support. |
We're sorry, CDN endpoint configuration changes are experiencing propagation delays | Check back here for status updates; If your configuration changes are not fully propagated in the expected time, contact support. |
We're sorry, we are experiencing issues loading the supplemental portal | Check back here for status updates; If your problem persists after the expected resolution time, contact support. |
We are sorry, we are experiencing issues with some of our CDN providers | Check back here for status updates; If your problem persists after the expected resolution time, contact support. |