Skip to content

Commit

Permalink
Fix broken link
Browse files Browse the repository at this point in the history
First link to "Enabling Diagnostics in Azure Cloud Services and Virtual Machines" was broken.  I updated it to mirror the later working example of the link later in the page.
  • Loading branch information
cilynx committed Mar 30, 2015
1 parent 0939f4a commit 756327e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion articles/cloud-services-how-to-monitor.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Monitoring displays in the Management Portal are highly configurable. You can ch
By default, minimal monitoring is provided for a new cloud service using performance counters gathered from the host operating system for the roles instances (virtual machines). The minimal metrics are limited to CPU Percentage, Data In, Data Out, Disk Read Throughput, and Disk Write Throughput. By configuring verbose monitoring, you can receive additional metrics based on performance data within the virtual machines (role instances). The verbose metrics enable closer analysis of issues that occur during application operations.

> [AZURE.NOTE]
> If you use verbose monitoring, you can add more performance counters at role instance startup, through a diagnostics configuration file. To be able to monitor these metrics in the Management Portal, you must add the performance counters before you configure verbose monitoring. For more information, see <a href="http://azure.microsoft.comcloud-services-dotnet-diagnostics.md">Enabling Diagnostics in Azure Cloud Services and Virtual Machines</a>.
> If you use verbose monitoring, you can add more performance counters at role instance startup, through a diagnostics configuration file. To be able to monitor these metrics in the Management Portal, you must add the performance counters before you configure verbose monitoring. For more information, see [Enabling Diagnostics in Azure Cloud Services and Virtual Machines](cloud-services-dotnet-diagnostics.md).
By default performance counter data from role instances is sampled and transferred from the role instance at 3-minute intervals. When you enable verbose monitoring, the raw performance counter data is aggregated for each role instance and across role instances for each role at intervals of 5 minutes, 1 hour, and 12 hours. The aggregated data is purged after 10 days.

Expand Down

0 comments on commit 756327e

Please sign in to comment.