Merge pull request #4620 from Azure/DailyPub

Daily pub

articles/api-management-howto-api-inspector.md

@@ -1,4 +1,4 @@
-<properties pageTitle="How to use the API Inspector to trace calls in Azure API Management" metaKeywords="" description="Learn how to trace calls using the API Inspector in Azure API Management." metaCanonical="" services="" documentationCenter="API Management" title="How to use the API Inspector to trace calls in Azure API Management" authors="sdanie" solutions="" manager="" editor="" />
+<properties pageTitle="How to use the API Inspector to trace calls in Azure API Management" metaKeywords="" description="Learn how to trace calls using the API Inspector in Azure API Management." metaCanonical="" services="api-management" documentationCenter="API Management" title="How to use the API Inspector to trace calls in Azure API Management" authors="sdanie" solutions="" manager="" editor="" />
 
 <tags ms.service="api-management" ms.workload="mobile" ms.tgt_pltfrm="na" ms.devlang="na" ms.topic="article" ms.date="01/01/1900" ms.author="sdanie" />
 

articles/app-insights-explore-metrics.md

@@ -11,6 +11,7 @@ Here are the reports you can expect to see on your application's blade in Applic
 
 + [Application Health](#health) 
 + [Usage Analytics](#usage)
++ [Video: Monitoring performance](#video)
 + [Next steps](#next)
 
 
@@ -60,6 +61,9 @@ If you've [set up diagnostic logging][diagnostic], click through to see the late
 
 A count of requests that threw uncaught exceptions.
 
+### <a name="video"></a>Monitoring performance
+
+[WACOM.VIDEO monitoring-performance-with-application-insights]
 
 ## <a name="usage"></a>Usage Analytics
 
@@ -79,10 +83,15 @@ Shows total counts in the last 24 hours.
 
 Click through to see graphs of page views over the past week.
 
-### Rearrange the tiles
+### Tracking usage
+[WACOM.VIDEO tracking-usage-with-application-insights]
+
+
+## Rearrange the tiles
 
 ![Choose settings, customize](./media/appinsights/appinsights-21-customizeblade.png)
 
+
 ## <a name="next"></a>Next steps
 
 [Set up web tests][availability]

articles/app-insights-get-started.md

@@ -40,6 +40,8 @@ There are two ways to get started:
 
 ![Example application monitor in Application Insights](./media/appinsights/appinsights-00-appblade.png)
 
+[WACOM.VIDEO application-insights-introduction]
+
 ## Learn more
 
 * [Application Insights][root]
@@ -60,5 +62,5 @@ There are two ways to get started:
 [explore]: ../app-insights-explore-metrics/
 [diagnostic]: ../app-insights-search-diagnostic-logs/ 
 [availability]: ../app-insights-monitor-web-app-availability/
-[usage]: ../app-insights-web-track-usage-custom-events-metrics/
+[usage]: ../app-insights-track-usage-custom-events-metrics/
 [qna]: ../app-insights-troubleshoot-faq/

articles/app-insights-monitor-application-health-usage.md

@@ -22,6 +22,7 @@ You'll need [Visual Studio Update 3](http://go.microsoft.com/fwlink/?LinkId=3978
 
 *Alternatively, if you want to monitor an existing web service without redeploying it or using Visual Studio, you can [install an agent on the server][redfield].*
 
+
 ## <a name="add"></a>1. Add Application Insights
 
 ### If it's a new project...
@@ -86,6 +87,9 @@ Run your application again and you'll see data in **Usage analytics**.
 
 Deploy your application and watch the data accumulate.
 
+## <a name="video"></a>Getting started with Application Insights
+
+[WACOM.VIDEO getting-started-with-application-insights]
 
 ## <a name="next"></a>Next steps
 

articles/app-insights-monitor-web-app-availability.md

@@ -13,6 +13,7 @@ You can set up web tests for any HTTP endpoint that is accessible from the publi
 + [Set up a web test](#setup)
 + [See monitor reports](#monitor)
 + [Edit or disable a test](#edit)
++ [Video: Monitoring availability](#video)
 + [Next steps](#next)
 
 
@@ -84,6 +85,9 @@ Open an individual test to edit or disable it.
 
 You might want to disable web tests while you are performing maintenance on your service.
 
+## <a name="video"></a>Monitoring availability
+[WACOM.VIDEO monitoring-availability-with-application-insights]
+
 ## <a name="next"></a>Next steps
 
 [Search diagnostic logs][diagnostic]

articles/app-insights-track-usage-custom-events-metrics.md

@@ -1,8 +1,30 @@
-<properties title="Track usage with custom events and metrics" pageTitle="Track usage with custom events and metrics" description="Log user activities." metaKeywords="analytics monitoring application insights" authors="awills"  />
+<properties title="Track usage with custom events and metrics" pageTitle="Track usage" description="Log user activities." metaKeywords="analytics monitoring application insights" authors="awills"  />
 
 <tags ms.service="application-insights" ms.workload="tbd" ms.tgt_pltfrm="ibiza" ms.devlang="na" ms.topic="article" ms.date="01/01/1900" ms.author="awills" />
 
-# Track usage with custom events and metrics
+# Track usage
+
+If you haven't yet [set up your web project for Application Insights][start], do that now.
+
+## <a name="usage"></a>Usage Analytics
+
+![](./media/appinsights/appinsights-47usage.png)
+
+Usage data comes partly from the server and partly from the [scripts in the web pages][start].
+
+### Sessions per browser
+
+A *session* is a period that starts when a user opens any page on your website, and ends after the user has not sent any web request for a timeout period of 30 minutes. 
+
+Click through to zoom into the chart.
+
+### Top page views
+
+Shows total counts in the last 24 hours.
+
+Click through to see graphs of page views over the past week.
+
+## Track usage with custom events and metrics
 
 ### Coming soon
 
@@ -13,6 +35,10 @@ We're currently still porting this feature over to the new Application Insights
 However, one thing you can do right now is to [capture and search diagnostic event logs generated with Trace, NLog or Log4Net][diagnostic]. 
 
 
+## Tracking usage
+
+[WACOM.VIDEO tracking-usage-with-application-insights]
+
 
 ## Application Insights
 

articles/azure-subscription-service-limits.md

@@ -13,7 +13,7 @@ The following document specifies some of the most common Microsoft Azure limits.
 - [Storage Limits](#storagelimits)
 - [SQL Database Limits](#sqldblimits)
 
-> [WACOM.NOTE] If you want to raise the limit above the **Default Limit**, open an incident with [customer support][customersupport]. The limits cannot be raised above the **Maximum Limit** value in the tables below. If there is no **Maximum Limit** column, then the specified resource does not have adjustable limits.
+> [WACOM.NOTE] If you want to raise the limit above the **Default Limit**, you can [open an online customer support request at no charge][azurelimitsblogpost]. The limits cannot be raised above the **Maximum Limit** value in the tables below. If there is no **Maximum Limit** column, then the specified resource does not have adjustable limits.
 
 ##<a name="subscription"></a>Subscription Limits
 
@@ -109,7 +109,7 @@ The following document specifies some of the most common Microsoft Azure limits.
 </tr>
 </table>
 
-<sup>1</sup>Each Cloud Service with Web/Worker roles can have two deployments, one for production and one for staging. 
+<sup>1</sup>Each Cloud Service with Web/Worker roles can have two deployments, one for production and one for staging. Also note that this limit refers to the number of distinct roles (configuration) and not the number of instances per role (scaling). 
 
 ##<a name="vmlimits"></a>Virtual Machine Limits
 
@@ -171,50 +171,80 @@ The following document specifies some of the most common Microsoft Azure limits.
 
 <sup>3</sup>ACL is supported on Input Endpoints for Virtual Machines. For web/worker roles, it is supported on Input and Instance Input endpoints.
 
-##<a name="storagelimits"></a>Storage Limits<sup>1</sup>
+##<a name="storagelimits"></a>Storage Limits
 
 <table cellspacing="0" border="1">
 <tr>
-   <th align="left" valign="middle">Resource</th>
+   <th align="left" valign="middle">Resource<sup>1</sup></th>
    <th align="left" valign="middle">Default Limit</th>
 </tr>
 <tr>
-   <td valign="middle"><p>TB per storage account<sup>2</sup></p></td>
-   <td valign="middle"><p>500</p></td>
+   <td valign="middle"><p>TB per storage account</p></td>
+   <td valign="middle"><p>500 TB</p></td>
 </tr>
 <tr>
-   <td valign="middle"><p>Max IOPS for persistent disk</p></td>
-   <td valign="middle"><p>500<sup>3</sup></p></td>
+   <td valign="middle"><p>Max size of a single blob container, table, or queue</p></td>
+   <td valign="middle"><p>500 TB</p></td>
 </tr>
 <tr>
-   <td valign="middle"><p>Max IOPS per storage account</p></td>
-   <td valign="middle"><p>20,000</p></td>
+   <td valign="middle"><p>Max number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account</p></td>
+   <td valign="middle"><p>Only limit is the 500 TB storage account capacity</p></td>
 </tr>
 <tr>
-   <td valign="middle"><p>Max ingress per storage account (US Regions)</p></td>
-   <td valign="middle"><p>10 Gbps if GRS<sup>4</sup> enabled, 20 Gbps with it disabled</p></td>
+   <td valign="middle"><p>Max size of a file share</p></td>
+   <td valign="middle"><p>5 TB</p></td>
 </tr>
 <tr>
-   <td valign="middle"><p>Max ingress per storage account (European and Asian Regions)</p></td>
-   <td valign="middle"><p>5 Gbps if GRS<sup>4</sup> enabled, 10 Gbps with it disabled</p></td>
+   <td valign="middle"><p>Max number of files in a file share</p></td>
+   <td valign="middle"><p>Only limit is the 5 TB total capacity of the file share</p></td>
+</tr>
+<tr>
+   <td valign="middle"><p>Max 8 KB IOPS per persistent disk (Basic Tier)</p></td>
+   <td valign="middle"><p>300<sup>2</sup></p></td>
+</tr>
+<tr>
+   <td valign="middle"><p>Max 8 KB IOPS per persistent disk (Standard Tier)</p></td>
+   <td valign="middle"><p>500<sup>2</sup></p></td>
+</tr>
+<tr>
+   <td valign="middle"><p>Total Request Rate (assuming 1KB object size) per storage account</p></td>
+   <td valign="middle"><p>Up to 20,000 entities or messages per second</p></td>
+</tr>
+<tr>
+   <td valign="middle"><p>Target Throughput for Single Blob</p></td>
+   <td valign="middle"><p>Up to 60 MB per second, or up to 500 requests per second</p></td>
+</tr>
+<tr>
+   <td valign="middle"><p>Target Throughput for Single Queue (1 KB messages)</p></td>
+   <td valign="middle"><p>Up to 2000 messages per second</p></td>
+</tr>
+<tr>
+   <td valign="middle"><p>Target Throughput for Single Table Partition (1 KB entities)</p></td>
+   <td valign="middle"><p>Up to 2000 entities per second</p></td>
+</tr>
+<tr>
+   <td valign="middle"><p>Max ingress per storage account (US Regions)</p></td>
+   <td valign="middle"><p>10 Gbps if GRS<sup>3</sup> enabled, 20 Gbps for LRS</p></td>
 </tr>
 <tr>
    <td valign="middle"><p>Max egress per storage account (US Regions)</p></td>
-   <td valign="middle"><p>20 Gbps if GRS<sup>4</sup> enabled, 30 Gbps with it disabled</p></td>
+   <td valign="middle"><p>20 Gbps if GRS<sup>3</sup> enabled, 30 Gbps for LRS</p></td>
+</tr>
+<tr>
+   <td valign="middle"><p>Max ingress per storage account (European and Asian Regions)</p></td>
+   <td valign="middle"><p>5 Gbps if GRS<sup>3</sup> enabled, 10 Gbps for LRS</p></td>
 </tr>
 <tr>
    <td valign="middle"><p>Max egress per storage account (European and Asian Regions)</p></td>
-   <td valign="middle"><p>10 Gbps if GRS<sup>4</sup> enabled, 15 Gbps with it disabled</p></td>
+   <td valign="middle"><p>10 Gbps if GRS<sup>3</sup> enabled, 15 Gbps for LRS</p></td>
 </tr>
 </table>
 
 <sup>1</sup>For more details on these limits, see [Azure Storage Scalability and Performance Targets][storagelimits]. 
 
-<sup>2</sup>For page blobs only pages that are in-use accrue capacity usage. For example, a Virtual Machine with a 127 GB VHD but with only 30 GB being used by the OS, is only billed for the used 30 GB portion within the VHD, not the entire 127 GB. 
+<sup>2</sup>For virtual machines in the Basic Tier, do not place more than 66 highly used VHDs in a storage account to avoid the 20,000 total request rate limit (20,000/300). For virtual machines in the Standard Tier, do not place more than 40 highly used VHDs in a storage account (20,000/500). For more information, see [Virtual Machine and Cloud Service Sizes for Azure][vmsizes]. 
 
-<sup>3</sup>Do not place more than 40 highly used VHDs in an account to avoid the 20,000 IOPS limit.
-
-<sup>4</sup>Geo-Redundant Storage Account
+<sup>3</sup>GRS is [Geo Redundant Storage][georedundantstorage]. LRS is [Locally Redundant Storage][locallyredundantstorage]. Note that GRS is also locally redundant.
 
 ##<a name="sqldblimits"></a>SQL Database Limits
 
@@ -226,6 +256,8 @@ For SQL Database Limits, please see the following topics:
 
 ##<a name="seealso"></a>See Also
 
+[Understanding Azure Limits and Increases][azurelimitsblogpost]
+
 [Virtual Machine and Cloud Service Sizes for Azure][vmsizes]
 
 [Azure Storage Scalability and Performance Targets][storagelimits]
@@ -236,11 +268,14 @@ For SQL Database Limits, please see the following topics:
 
 [SQL Database Resource Limits][sqldblimits]
 
-  [customersupport]: http://azure.microsoft.com/en-us/support/faq/
+  [customersupportfaq]: http://azure.microsoft.com/en-us/support/faq/
+  [azurelimitsblogpost]: http://azure.microsoft.com/blog/2014/06/04/azure-limits-quotas-increase-requests/
   [gateway]: http://msdn.microsoft.com/en-us/library/azure/jj156210.aspx 
   [storagelimits]: http://msdn.microsoft.com/library/azure/dn249410.aspx
   [georedundantstorage]: http://blogs.msdn.com/b/windowsazurestorage/archive/2011/09/15/introducing-geo-replication-for-windows-azure-storage.aspx
   [sqldblimits]: http://msdn.microsoft.com/en-us/library/azure/dn338081.aspx
   [sqltiers]: http://msdn.microsoft.com/en-us/library/azure/dn741340.aspx
   [sqltiersperflevels]: http://msdn.microsoft.com/en-us/library/azure/dn741336.aspx
   [vmsizes]: http://msdn.microsoft.com/en-us/library/azure/dn197896.aspx
+  [georedundantstorage]: http://blogs.msdn.com/b/windowsazurestorage/archive/2011/09/15/introducing-geo-replication-for-windows-azure-storage.aspx
+  [locallyredundantstorage]: http://blogs.msdn.com/b/windowsazurestorage/archive/2012/06/08/introducing-locally-redundant-storage-for-windows-azure-storage.aspx

articles/command-line-tools.md

@@ -650,10 +650,12 @@ This command lists Azure cloud services.
 
 This command deletes an Azure cloud service.
 
-	~$ azure cloud-service delete myservice
-	info:   Executing command cloud-service delete myservice 
+	~$ azure service delete myservice
+	info:   Executing command service delete myservice 
 	info:   cloud-service delete command OK
 
+To force the deletion, use the `-q` parameter.
+
 
 ##<a name="Commands_to_manage_your_Azure_certificates"></a>Commands to manage your Azure certificates