Merge pull request #114655 from mrbullwinkle/mrb_05_08_2020_APM_2_1

Application Insights workspace-enabled resources

Author: v-shmck

articles/azure-monitor/app/apm-tables.md

@@ -22,9 +22,10 @@ Sign in to the [Azure portal](https://portal.azure.com), and create an Applicati
 
    | Settings        |  Value           | Description  |
    | ------------- |:-------------|:-----|
-   | **Name**      | Unique value | Name that identifies the app you are monitoring. |
-   | **Resource Group**     | myResourceGroup      | Name for the new or existing resource group to host App Insights data. |
-   | **Location** | East US | Choose a location near you, or near where your app is hosted. |
+   | **Name**      | `Unique value` | Name that identifies the app you are monitoring. |
+   | **Resource Group**     | `myResourceGroup`      | Name for the new or existing resource group to host App Insights data. |
+   | **Region** | `East US` | Choose a location near you, or near where your app is hosted. |
+   | **Resource Mode** | `Classic` or `Workspace-based` | Workspace-based resources are currently in public preview and allow you to send your Application Insights telemetry to a common Log Analytics workspace. For more information, see the [article on workspace-based resources](create-workspace-resource.md).
 
 > [!NOTE]
 > While you can use the same resource name across different resource groups, it can be beneficial to use a globally unique name. This can be useful if you plan to [perform cross resource queries](https://docs.microsoft.com/azure/azure-monitor/log-query/cross-workspace-query#identifying-an-application) as it simplifies the required syntax.
@@ -92,13 +93,13 @@ For the full PowerShell documentation for this cmdlet, and to learn how to retri
 
 ### Azure CLI (preview)
 
-To access the preview Application Insights Azure CLI commands you first need to run:
+To access the preview Application Insights Azure CLI commands, you first need to run:
 
 ```azurecli
  az extension add -n application-insights
 ```
 
-If you don't run the `az extension add` command you will see an error message that states: `az : ERROR: az monitor: 'app-insights' is not in the 'az monitor' command group. See 'az monitor --help'.`
+If you don't run the `az extension add` command, you will see an error message that states: `az : ERROR: az monitor: 'app-insights' is not in the 'az monitor' command group. See 'az monitor --help'.`
 
 Now you can run the following to create your Application Insights resource:
 

articles/azure-monitor/app/create-new-resource.md

@@ -0,0 +1,200 @@
+---
+title: Create a new Azure Monitor Application Insights workspace-based resource | Microsoft Docs
+description: Learn about the steps required to enable the new Azure Monitor Application Insights workspace-based resources. 
+author: mrbullwinkle
+ms.author: mbullwin
+ms.topic: conceptual
+ms.date: 12/02/2019
+
+---
+
+# Workspace-based Application Insights resources (preview)
+
+Workspace-based resources support full integration between Application Insights and Log Analytics. You can now choose to send your Application Insights telemetry to a common Log Analytics workspace, which allows you full access to all the features of Log Analytics while keeping application, infrastructure, and platform logs in a single consolidated location.
+
+This also allows for common Role-Based Access Control (RBAC) across your resources, and eliminates the need for cross-app/workspace queries.
+
+> [!NOTE]
+> Data ingestion and retention for workspace-based Application Insights resources are billed through the Log Analytics workspace where the data is located. [Learn more]( https://docs.microsoft.com/azure/azure-monitor/app/pricing#workspace-based-application-insights) about billing for workspace-based Application Insights resources.
+
+To test out the new experience, sign in to the [Azure portal](https://portal.azure.com), and create an Application Insights resource:
+
+![Workspace-based Application Insights resource](./media/create-workspace-resource/create-workspace-based.png)
+
+If you don't already have an existing Log Analytics Workspace, [consult the Log Analytics workspace creation documentation](https://docs.microsoft.com/azure/azure-monitor/learn/quick-create-workspace).
+
+For the public preview **workspace-based resources are currently limited to West US 2, East US, and South Central US.**
+
+Once your resource is created, you will see the corresponding workspace info in the **Overview** pane:
+
+![Workspace Name](./media/create-workspace-resource/workspace-name.png)
+
+Clicking the blue link text will take you to the associated Log Analytics workspace where you can take advantage of the new unified workspace query environment.
+
+> [!NOTE]
+> We still provide full backwards compatibility for your Application Insights classic resource queries, workbooks, and log-based alerts within the Application Insights experience. To query/view against the [new workspace-based table structure/schema](apm-tables.md) you must first navigate to your Log Analytics workspace. During the preview, selecting **Logs** from within the Application Insights panes will give you access to the classic Application Insights query experience.
+
+## Copy the connection string
+
+The [connection string]() identifies the resource that you want to associate your telemetry data with. It also allows you to modify the endpoints your resource will use as a destination for your telemetry. You will need to copy the connection string and add it to your application's code or to an environment variable.
+
+![Click and copy the instrumentation key](./media/create-new-resource/instrumentation-key.png)
+
+## Monitoring configuration
+
+Once a workspace-based Application Insights resource has been created, configuring monitoring is relatively straightforward.
+
+### Code-based application monitoring
+
+For code-based application monitoring, you would just install the appropriate Application Insights SDK and point it to the instrumentation key or connection string to your newly created resource.  
+
+For detailed documentation on setting up an Application Insights SDK for code-based monitoring consult the language/framework specific documentation:
+
+- [ASP.NET](https://docs.microsoft.com/azure/azure-monitor/app/asp-net)
+- [ASP.NET Core ](https://docs.microsoft.com/azure/azure-monitor/app/asp-net-core)
+- [Background tasks & modern console applications (.NET/.NET Core)](https://docs.microsoft.com/azure/azure-monitor/app/worker-service)
+- [Classic console applications (.NET)](https://docs.microsoft.com/azure/azure-monitor/app/console) 
+- [Java ](https://docs.microsoft.com/azure/azure-monitor/app/java-get-started?tabs=maven)
+- [JavaScript](https://docs.microsoft.com/azure/azure-monitor/app/javascript)
+- [Node.js](https://docs.microsoft.com/azure/azure-monitor/app/nodejs)
+- [Python](https://docs.microsoft.com/azure/azure-monitor/app/opencensus-python)
+
+### Codeless monitoring and Visual Studio resource creation
+
+For codeless monitoring of services like Azure Functions and Azure App Services, you will also need to first create your workspace-based Application Insights resource and then point to that resource during the monitoring configuration phase.
+
+While these services offer the option to create a new Application Insights resource within their own resource creation process, resources created via these UI options are currently restricted to the classic Application Insights experience.
+
+The same applies to the Application Insights resource creation experience in Visual Studio for ASP.NET and ASP.NET Core. You must select an existing workspace-based resource from with the Visual Studio monitoring enablement UI. Selecting create new resource from within Visual Studio will limit you to creating a classic Application Insights resource.
+
+## Creating a resource automatically
+
+### Azure CLI
+
+To access the preview Application Insights Azure CLI commands, you first need to run:
+
+```azurecli
+ az extension add -n application-insights
+```
+
+If you don't run the `az extension add` command, you will see an error message that states: `az : ERROR: az monitor: 'app-insights' is not in the 'az monitor' command group. See 'az monitor --help'.`
+
+Now you can run the following to create your Application Insights resource:
+
+```azurecli
+az monitor app-insights component create --app
+                                         --location
+                                         --resource-group
+                                         [--application-type]
+                                         [--ingestion-access {Disabled, Enabled}]
+                                         [--kind]
+                                         [--only-show-errors]
+                                         [--query-access {Disabled, Enabled}]
+                                         [--tags]
+                                         [--workspace]
+```
+
+#### Example
+
+```azurecli
+az monitor app-insights component create --app demoApp --location eastus --kind web -g my_resource_group --workspace "/subscriptions/00000000-0000-0000-0000-000000000000/resourcegroups/test1234/providers/microsoft.operationalinsights/workspaces/test1234555"
+```
+
+For the full Azure CLI documentation for this command,  consult the [Azure CLI documentation](https://docs.microsoft.com/cli/azure/ext/application-insights/monitor/app-insights/component?view=azure-cli-latest#ext-application-insights-az-monitor-app-insights-component-create).
+
+### Azure PowerShell
+
+The `New-AzApplicationInsights` PowerShell command does not currently support creating a workspace-based Application Insights resource. To create a workspace-based resource with PowerShell, you can use the Azure Resource Manager templates below and deploy with PowerShell.
+
+### Azure Resource Manager templates
+
+#### Template file
+
+```json
+{
+    "$schema": "http://schema.management.azure.com/schemas/2014-04-01-preview/deploymentTemplate.json#",
+    "contentVersion": "1.0.0.0",
+    "parameters": {
+        "name": {
+            "type": "string"
+        },
+        "type": {
+            "type": "string"
+        },
+        "regionId": {
+            "type": "string"
+        },
+        "tagsArray": {
+            "type": "object"
+        },
+        "requestSource": {
+            "type": "string"
+        },
+        "workspaceResourceId": {
+            "type": "string"
+        }
+    },
+    "resources": [
+        {
+            "name": "[parameters('name')]",
+            "type": "microsoft.insights/components",
+            "location": "[parameters('regionId')]",
+            "tags": "[parameters('tagsArray')]",
+            "apiVersion": "2020-02-02-preview",
+            "properties": {
+                "ApplicationId": "[parameters('name')]",
+                "Application_Type": "[parameters('type')]",
+                "Flow_Type": "Redfield",
+                "Request_Source": "[parameters('requestSource')]",
+                "WorkspaceResourceId": "[parameters('workspaceResourceId')]"
+            }
+        }
+    ]
+}
+```
+
+#### Parameters file
+
+```json
+{
+    "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
+    "contentVersion": "1.0.0.0",
+    "parameters": {
+        "type": {
+            "value": "web"
+        },
+        "name": {
+            "value": "customresourcename"
+        },
+        "regionId": {
+            "value": "eastus"
+        },
+        "tagsArray": {
+            "value": {}
+        },
+        "requestSource": {
+            "value": "Custom"
+        },
+        "workspaceResourceId": {
+            "value": "/subscriptions/00000000-0000-0000-0000-000000000000/resourcegroups/my_resource_group/providers/microsoft.operationalinsights/workspaces/myworkspacename"
+        }
+    }
+}
+
+```
+
+## Modifying the associated workspace
+
+Once a workspace-based Application Insights resource has been created, you can modify the associated Log Analytics Workspace.
+
+From within the Application Insights resource pane, select **Properties** > **Change Workspace** > **Log Analytics Workspaces**
+
+## Next steps
+
+* [Explore metrics](../../azure-monitor/platform/metrics-charts.md)
+* [Write Analytics queries](../../azure-monitor/app/analytics.md)
+
+[api]: ../../azure-monitor/app/api-custom-events-metrics.md
+[diagnostic]: ../../azure-monitor/app/diagnostic-search.md
+[metrics]: ../../azure-monitor/platform/metrics-charts.md
+[start]: ../../azure-monitor/app/app-insights-overview.md

articles/azure-monitor/app/create-workspace-resource.md

@@ -26,6 +26,10 @@ The pricing for [Azure Application Insights][start] is a **Pay-As-You-Go** model
 
 The Application Insights option to [Enable alerting on custom metric dimensions](https://docs.microsoft.com/azure/azure-monitor/app/pre-aggregated-metrics-log-metrics#custom-metrics-dimensions-and-pre-aggregation) can also generate in additional costs because this can result in the creation of additional pre-aggregation metrics. [Learn more](https://docs.microsoft.com/azure/azure-monitor/app/pre-aggregated-metrics-log-metrics) about log-based and pre-aggregated metrics in Application Insights and about [pricing](https://azure.microsoft.com/pricing/details/monitor/) for Azure Monitor custom metrics.
 
+### Workspace-based Application Insights
+
+For Application Insights resources which send their data to a Log Analytics workspace, called [workspace-based Application Insights resources](create-workspace-resource.md), the billing for data ingestion and retention is done by the workspace where the Application Insights data is located. This enables customers to leverage all options of the Log Analytics [pricing model](https://docs.microsoft.com/azure/azure-monitor/platform/manage-cost-storage#pricing-model) that includes Capacity Reservations in addition to Pay-As-You-Go. Log Analytics also has more options for data retention, including [retention by data type](https://docs.microsoft.com/azure/azure-monitor/platform/manage-cost-storage#retention-by-data-type). Application Insights data types in the workspace receive 90 days of retention without charges. Usage of web tests and enabling alerting on custom metric dimensions is still reported through Application Insights. Learn how to track data ingestion and retention costs in Log Analytics using the [Usage and estimated costs](https://docs.microsoft.com/azure/azure-monitor/platform/manage-cost-storage#understand-your-usage-and-estimate-costs), [Azure Cost Management + Billing](https://docs.microsoft.com/azure/azure-monitor/platform/manage-cost-storage#viewing-log-analytics-usage-on-your-azure-bill) and [Log Analytics queries](#data-volume-for-workspace-based-application-insights-resources). 
+
 ## Estimating the costs to manage your application
 
 If you're not yet using Application Insights, you can use the [Azure Monitor pricing calculator](https://azure.microsoft.com/pricing/calculator/?service=monitor) to estimate the cost of using Application Insights. Start by entering "Azure Monitor" in the Search box, and clicking on the resulting Azure Monitor tile. Scroll down the page to Azure Monitor, and select Application Insights from the Type dropdown.  Here you can enter the number of GB of data you expect to collect per month, so the question is how much data will Application Insights collect monitoring your application.
@@ -71,7 +75,7 @@ To learn more about your data volumes, selecting **Metrics** for your Applicatio
 
 ### Queries to understand data volume details
 
-There are two approaches to investigating data volumes for Application Insights. The first uses aggregated information in the `systemEvents` table, and the second uses the `_BilledSize` property, which is available on each ingested event.
+There are two approaches to investigating data volumes for Application Insights. The first uses aggregated information in the `systemEvents` table, and the second uses the `_BilledSize` property, which is available on each ingested event. `systemEvents` will not have data size information for [workspace-based-application-insights](#data-volume-for-workspace-based-application-insights-resources).
 
 #### Using aggregated data volume information
 
@@ -123,6 +127,47 @@ dependencies
 | render barchart  
 ```
 
+#### Data volume for workspace-based Application Insights resources
+
+To look at the data volume trends for all of the [workspace-based Application Insights resources](create-workspace-resource.md) in a workspace for the last week, go to the Log Analytics workspace and run the query:
+
+```kusto
+union (AppAvailabilityResults),
+      (AppBrowserTimings),
+      (AppDependencies),
+      (AppExceptions),
+      (AppEvents),
+      (AppMetrics),
+      (AppPageViews),
+      (AppPerformanceCounters),
+      (AppRequests),
+      (AppSystemEvents),
+      (AppTraces)
+| where TimeGenerated >= startofday(ago(7d) and TimeGenerated < startofday(now())
+| summarize sum(_BilledSize) by _ResourceId, bin(TimeGenerated, 1d)
+| render areachart
+```
+
+To query the data volume trends by type for a specific workspace-based Application Insights resource, in the Log Analytics workspace use:
+
+```kusto
+union (AppAvailabilityResults),
+      (AppBrowserTimings),
+      (AppDependencies),
+      (AppExceptions),
+      (AppEvents),
+      (AppMetrics),
+      (AppPageViews),
+      (AppPerformanceCounters),
+      (AppRequests),
+      (AppSystemEvents),
+      (AppTraces)
+| where TimeGenerated >= startofday(ago(7d) and TimeGenerated < startofday(now())
+| where _ResourceId contains "<myAppInsightsResourceName>"
+| summarize sum(_BilledSize) by Type, bin(TimeGenerated, 1d)
+| render areachart
+```
+
 ## Viewing Application Insights usage on your Azure bill
 
 Azure provides a great deal of useful functionality in the [Azure Cost Management + Billing](https://docs.microsoft.com/azure/cost-management/quick-acm-cost-analysis?toc=/azure/billing/TOC.json) hub. For instance, the "Cost analysis" functionality enables you to view your spends for Azure resources. Adding a filter by resource type (to microsoft.insights/components for Application Insights) will allow you to track your spending. Then for "Group by" select "Meter category" or "Meter".  For Application Insights resources on the current pricing plans, most usage will show up as Log Analytics for the Meter category since there is a single logs backend for all Azure Monitor components. 
@@ -174,7 +219,7 @@ To [change the daily cap via Azure Resource Manager](../../azure-monitor/app/pow
 
 ### Create alerts for the Daily Cap
 
-The Application Insights Daily Cap creates an event in the Azure activity log when the ingested data volumes hits the warning level or the daily cap level.  You can [create an alert based on these activity log events](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-activity-log#create-with-the-azure-portal). The signal names for these events are:
+The Application Insights Daily Cap creates an event in the Azure activity log when the ingested data volumes reaches the warning level or the daily cap level.  You can [create an alert based on these activity log events](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-activity-log#create-with-the-azure-portal). The signal names for these events are:
 
 * Application Insights component daily cap warning threshold reached