You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn about the new table structure and schema for Azure Monitor Application Insights workspace-based resources.
4
4
ms.topic: conceptual
5
-
ms.date: 07/01/2019
5
+
author: mrbullwinkle
6
+
ms.author: mbullwin
7
+
ms.date: 05/09/2020
6
8
7
9
---
8
10
9
-
# T
11
+
# Workspace-based resource changes (preview)
10
12
13
+
Prior to the introduction of [workspace-based Application Insights resources](create-workspace-resource.md), Application Insights data was stored separate from other log data in Azure Monitor. Both are based on Azure Data Explorer and use the same Kusto Query Language (KQL). This is described in [Logs in Azure Monitor](https://docs.microsoft.com/azure/azure-monitor/platform/data-platform-logs).
11
14
12
-
## AppAvailabilityResults
15
+
With workspace-based Application Insights resources data is stored in a Log Analytics workspace with other monitoring data and application data. This simplifies your configuration by allowing you to more easily analyze data across multiple solutions and to leverage the capabilities of workspaces.
16
+
17
+
## Table structure
18
+
19
+
| Legacy table name | New table name | Description |
20
+
|:---|:---|:---|
21
+
| availabilityResults | AppAvailabilityResults | Summary data from availability tests.|
22
+
| browserTimings | AppBrowserTimings | Data about client performance, such as the time taken to process the incoming data.|
23
+
| dependencies | AppDependencies | Calls from the application to other components (including external components) recorded via TrackDependency() – for example, calls to REST API, database or a file system. |
24
+
| customEvents | AppEvents | Custom events created by your application. |
25
+
| customMetrics | AppMetrics | Custom metrics created by your application. |
26
+
| pageViews | AppPageViews| Data about each website view with browser information. |
27
+
| performanceCounters | AppPerformanceCounters | Performance measurements from the compute resources supporting the application, for example, Windows performance counters. |
28
+
| requests | AppRequests | Requests received by your application. For example, a separate request record is logged for each HTTP request that your web app receives. |
29
+
| exceptions | AppSystemEvents | Exceptions thrown by the application runtime, captures both server side and client-side (browsers) exceptions. |
30
+
| traces | AppTraces | Detailed logs (traces) emitted through application code/logging frameworks recorded via TrackTrace(). |
31
+
32
+
## Table schemas
33
+
34
+
The following sections show the mapping between the classic property names and the new workspace-based Application Insights property names. Use this information to convert any queries using legacy tables.
35
+
36
+
Most of the columns have the same name with different capitalization. Since KQL is case-sensitive, you will need to change each column name along with the table names in existing queries. Columns with changes in addition to capitalization are highlighted. You can still use your classic Application Insights queries within the **Logs** pane of your Application Insights resource, even if it is a workspace-based resource. The new property names are required for when querying from within the context of the Log Analytics workspace experience.
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/create-workspace-resource.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Create a new Azure Application Insights resource | Microsoft Docs
3
-
description: Manually set up Application Insights monitoring for a new live application.
2
+
title: Create a new Azure Monitor Application Insights workspace-based resource | Microsoft Docs
3
+
description: Learn about the steps required to enable the new Azure Monitor Application Insights workspace-based resources.
4
4
author: mrbullwinkle
5
5
ms.author: mbullwin
6
6
ms.topic: conceptual
@@ -32,7 +32,7 @@ Once your resource is created, you will see the corresponding workspace info in
32
32
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.
33
33
34
34
> [!NOTE]
35
-
> 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 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.
35
+
> 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.
36
36
37
37
## Copy the connection string
38
38
@@ -42,7 +42,7 @@ The [connection string]() identifies the resource that you want to associate you
42
42
43
43
## Monitoring configuration
44
44
45
-
Once a workspace-based Application Insights resource has been created, configuring monitoring is relatively straightforward.
45
+
Once a workspace-based Application Insights resource has been created, configuring monitoring is relatively straightforward.
46
46
47
47
### Code-based application monitoring
48
48
@@ -65,7 +65,7 @@ For codeless monitoring of services like Azure Functions and Azure App Services,
65
65
66
66
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.
67
67
68
-
The same applies to the resource creation experience in Visual Studio. 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 create a classic Application Insights resource.
68
+
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.
Copy file name to clipboardExpand all lines: articles/azure-monitor/log-query/app-expression.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ ms.subservice: logs
5
5
ms.topic: conceptual
6
6
author: bwren
7
7
ms.author: bwren
8
-
ms.date: 05/01/2019
8
+
ms.date: 05/09/2019
9
9
10
10
---
11
11
@@ -14,7 +14,7 @@ ms.date: 05/01/2019
14
14
The `app` expression is used in an Azure Monitor query to retrieve data from a specific Application Insights app in the same resource group, another resource group, or another subscription. This is useful to include application data in an Azure Monitor log query and to query data across multiple applications in an Application Insights query.
15
15
16
16
> [!IMPORTANT]
17
-
> The app() expression is not used if you're using APM 2.1 since Application Insights log data is stored in a Log Analytics workspace. Use the log() expression to write a query that includes application in multiple workspaces. For multiple applications in the same workspace, you don't need a cross workspace query.
17
+
> The app() expression is not used if you're using a [workspace-based Application Insights resource](../app/create-workspace-resource.md) since log data is stored in a Log Analytics workspace. Use the log() expression to write a query that includes application in multiple workspaces. For multiple applications in the same workspace, you don't need a cross workspace query.
Copy file name to clipboardExpand all lines: articles/azure-monitor/log-query/cross-workspace-query.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.date: 05/01/2020
12
12
# Perform cross-resource log queries in Azure Monitor
13
13
14
14
> [!IMPORTANT]
15
-
> If you are using APM 2.1, then Application Insights applications are stored in a Log Analytics workspace with all other log data. Use the log() expression to write a query that includes application in multiple workspaces. For multiple applications in the same workspace, you don't need a cross workspace query.
15
+
> If you are using a [workspace-based Application Insights resource](../app/create-workspace-resource.md) telemetry is stored in a Log Analytics workspace with all other log data. Use the log() expression to write a query that includes application in multiple workspaces. For multiple applications in the same workspace, you don't need a cross workspace query.
16
16
17
17
Previously with Azure Monitor, you could only analyze data from within the current workspace, and it limited your ability to query across multiple workspaces defined in your subscription. Additionally, you could only search telemetry items collected from your web-based application with Application Insights directly in Application Insights or from Visual Studio. This also made it a challenge to natively analyze operational and application data together.
Copy file name to clipboardExpand all lines: articles/azure-monitor/log-query/logs-structure.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ ms.subservice: logs
5
5
ms.topic: conceptual
6
6
author: bwren
7
7
ms.author: bwren
8
-
ms.date: 05/01/2020
8
+
ms.date: 05/09/2020
9
9
10
10
---
11
11
@@ -16,7 +16,7 @@ The ability to quickly gain insights into your data using a [log query](log-quer
16
16
Data in Azure Monitor Logs is stored in either a Log Analytics workspace or an Application Insights application. Both are powered by [Azure Data Explorer](/azure/data-explorer/) meaning that they leverage its powerful data engine and query language.
17
17
18
18
> [!IMPORTANT]
19
-
> If you are using APM 2.1, then Application Insights applications are stored in a Log Analytics workspace with all other log data. The tables have been renamed and restructured but have the same information as the tables in the Application Insights application.
19
+
> If you are using a [workspace-based Application Insights resource](../app/create-workspace-resource.md), telemetry is stored in a Log Analytics workspace with all other log data. The tables have been renamed and restructured but have the same information as the tables in the Application Insights application.
20
20
21
21
Data in both workspaces and applications is organized into tables, each of which stores different kinds of data and has its own unique set of properties. Most [data sources](../platform/data-sources.md) will write to their own tables in a Log Analytics workspace, while Application Insights will write to a predefined set of tables in an Application Insights application. Log queries are very flexible allowing you to easily combine data from multiple tables and even use a cross-resource query to combine data from tables in multiple workspaces or to write queries that combine workspace and application data.
22
22
@@ -49,7 +49,7 @@ See [Designing an Azure Monitor Logs deployment](../platform/design-logs-deploym
49
49
## Application Insights application
50
50
51
51
> [!IMPORTANT]
52
-
> If you are using APM 2.1, then Application Insights applications are stored in a Log Analytics workspace with all other log data. The tables have been renamed and restructured but have the same information as the tables in the Application Insights application.
52
+
> If you are using a [workspace-based Application Insights resource](../app/create-workspace-resource.md) telemetry is stored in a Log Analytics workspace with all other log data. The tables have been renamed and restructured but have the same information as the tables in a classic Application Insights resource.
53
53
54
54
When you create an application in Application Insights, a corresponding application is automatically created in Azure Monitor Logs. No configuration is required to collect data, and the application will automatically write monitoring data such as page views, requests, and exceptions.
55
55
@@ -61,12 +61,12 @@ Unlike a Log Analytics workspace, an Application Insights application has a fixe
61
61
| browserTimings | Data about client performance, such as the time taken to process the incoming data. |
62
62
| customEvents | Custom events created by your application. |
63
63
| customMetrics | Custom metrics created by your application. |
64
-
| dependencies | Calls from the application to external components. |
65
-
| exceptions | Exceptions thrown by the application runtime. |
64
+
| dependencies | Calls from the application to other components (including external components) recorded via TrackDependency() – for example, calls to REST API, database or a file system. |
65
+
| exceptions | Exceptions thrown by the application runtime, captures both server side and client-side (browsers) exceptions.|
66
66
| pageViews | Data about each website view with browser information. |
67
-
| performanceCounters | Performance measurements from the compute resources supporting the application. |
68
-
| requests |Details of each applicationrequest. |
69
-
| traces |Results from distributed tracing. |
67
+
| performanceCounters | Performance measurements from the compute resources supporting the application, for example, Windows performance counters. |
68
+
| requests |Requests received by your application. For example, a separate request record is logged for each HTTP request that your web app receives. |
69
+
| traces |Detailed logs (traces) emitted through application code/logging frameworks recorded via TrackTrace(). |
70
70
71
71
You can view the schema for each table in the **Schema** tab in Log Analytics for the application.
0 commit comments