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
title: Azure Application Insights Telemetry Data Model - Event Telemetry | Microsoft Docs
3
-
description: Application Insights data model for event telemetry
2
+
title: Application Insights telemetry data model - Event telemetry | Microsoft Docs
3
+
description: Learn about the Application Insights data model for event telemetry.
4
4
ms.topic: conceptual
5
5
ms.date: 04/25/2017
6
6
ms.reviewer: mmcc
7
7
---
8
8
9
9
# Event telemetry: Application Insights data model
10
10
11
-
You can create event telemetry items (in [Application Insights](./app-insights-overview.md)) to represent an event that occurred in your application. Typically it is a user interaction such as button click or order checkout. It can also be an application life cycle event like initialization or configuration update.
11
+
You can create event telemetry items (in [Application Insights](./app-insights-overview.md)) to represent an event that occurred in your application. Typically, it's a user interaction such as a button click or order checkout. It can also be an application lifecycle event like initialization or a configuration update.
12
12
13
-
Semantically, events may or may not be correlated to requests. However, if used properly, event telemetry is more important than requests or traces. Events represent business telemetry and should be a subject to separate, less aggressive [sampling](./api-filtering-sampling.md).
13
+
Semantically, events may or may not be correlated to requests. However, if used properly, event telemetry is more important than requests or traces. Events represent business telemetry and should be subject to separate, less aggressive [sampling](./api-filtering-sampling.md).
14
14
15
15
## Name
16
16
17
-
Event name. To allow proper grouping and useful metrics, restrict your application so that it generates a small number of separate event names. For example, don't use a separate name for each generated instance of an event.
17
+
Event name: To allow proper grouping and useful metrics, restrict your application so that it generates a few separate event names. For example, don't use a separate name for each generated instance of an event.
18
18
19
-
Max length: 512 characters
19
+
**Maximum length:** 512 characters
20
20
21
21
## Custom properties
22
22
@@ -28,7 +28,6 @@ Max length: 512 characters
28
28
29
29
## Next steps
30
30
31
-
- See [data model](data-model.md) for Application Insights types and data model.
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/sharepoint.md
+28-27Lines changed: 28 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,28 @@
1
1
---
2
2
title: Monitor a SharePoint site with Application Insights
3
-
description: Start monitoring a new application with a new instrumentation key
3
+
description: Start monitoring a new application with a new instrumentation key.
4
4
ms.topic: conceptual
5
5
ms.date: 09/08/2020
6
6
ms.reviewer: newylie
7
7
---
8
8
9
9
# Monitor a SharePoint site with Application Insights
10
10
11
-
Azure Application Insights monitors the availability, performance and usage of your apps. Here you'll learn how to set it up for a SharePoint site.
11
+
Application Insights monitors the availability, performance, and usage of your apps. This article shows you how to set it up for a SharePoint site.
12
12
13
13
> [!NOTE]
14
-
> Due to security concerns, you can't directly add the script that's described in this article to your webpages in the SharePoint modern UX. As an alternative, you can use [SharePoint Framework (SPFx)](/sharepoint/dev/spfx/extensions/overview-extensions) to build a custom extension that you can use to install Application Insights on your SharePoint sites.
14
+
> Because of security concerns, you can't directly add the script that's described in this article to your webpages in the SharePoint modern UX. As an alternative, you can use [SharePoint Framework (SPFx)](/sharepoint/dev/spfx/extensions/overview-extensions) to build a custom extension that you can use to install Application Insights on your SharePoint sites.
15
15
16
16
## Create an Application Insights resource
17
17
In the [Azure portal](https://portal.azure.com), create a new Application Insights resource. Choose ASP.NET as the application type.
18
18
19
-
19
+
20
20
21
-
The window that opens is the place where you'll see performance and usage data about your app. To get back to it next time you sign in to Azure, you should find a tile for it on the start screen. Alternatively select Browse to find it.
21
+
The window that opens is the place where you see performance and usage data about your app. The next time you sign in to Azure, a tile for it appears on the **Start** screen. Alternatively, select **Browse** to find it.
22
22
23
-
## Add the script to your web pages
23
+
## Add the script to your webpages
24
24
25
-
The current Snippet (listed below) is version "5", the version is encoded in the snippet as sv:"#" and the[current version is also available on GitHub](https://go.microsoft.com/fwlink/?linkid=2156318).
25
+
The following current snippet is version `"5"`. The version is encoded in the snippet as `sv:"#"`. The[current version is also available on GitHub](https://go.microsoft.com/fwlink/?linkid=2156318).
> The Url for SharePoint uses a different module format "...\ai.2.gbl.min.js" (note the additional **.gbl.**) this alternate module format is required to avoid an issue caused by the order that scripts are loaded, which will cause the SDK to fail to initialize and will result in the loss of telemetry events.
50
+
> The URL for SharePoint uses a different module format "...\ai.2.gbl.min.js" (note the additional **.gbl.**). This alternate module format is required to avoid an issue caused by the order that scripts are loaded, which will cause the SDK to fail to initialize and result in the loss of telemetry events.
51
51
>
52
-
> The issue is caused by requireJS being loaded and initialized before the SDK.
52
+
> The issue is caused by `requireJS` being loaded and initialized before the SDK.
53
53
54
-
Insert the script just before the </head> tag of every page you want to track. If your website has a master page, you can put the script there. For example, in an ASP.NET MVC project, you'd put it in View\Shared\_Layout.cshtml
54
+
Insert the script before the </head> tag of every page you want to track. If your website has a main page, you can put the script there. For example, in an ASP.NET MVC project, you'd put it in `View\Shared\_Layout.cshtml`.
55
55
56
56
The script contains the instrumentation key that directs the telemetry to your Application Insights resource.
57
57
58
58
### Add the code to your site pages
59
-
#### On the master page
60
-
If you can edit the site's master page, that will provide monitoring for every page in the site.
61
59
62
-
Check out the master page and edit it using SharePoint Designer or any other editor.
60
+
You can add the code to your main page or individual pages.
63
61
64
-
62
+
#### Main page
63
+
If you can edit the site's main page, that will provide monitoring for every page in the site.
65
64
66
-
Add the code just before the </head> tag.
65
+
Check out the main page and edit it by using SharePoint Designer or any other editor.
66
+
67
+
68
+
69
+
Add the code before the </head> tag.
67
70
68
71
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/source-map-support.md
+38-36Lines changed: 38 additions & 36 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
2
title: Source map support for JavaScript applications - Azure Monitor Application Insights
3
-
description: Learn how to upload source maps to your own storage account Blob container using Application Insights.
3
+
description: Learn how to upload source maps to your Azure Storage account blob container by using Application Insights.
4
4
ms.topic: conceptual
5
5
ms.date: 06/23/2020
6
6
ms.custom: devx-track-js
@@ -9,76 +9,78 @@ ms.reviewer: mmcc
9
9
10
10
# Source map support for JavaScript applications
11
11
12
-
Application Insights supports the uploading of source maps to your own Storage Account Blob Container.
13
-
Source maps can be used to unminify call stacks found on the end to end transaction details page. Any exception sent by the [JavaScript SDK][ApplicationInsights-JS] or the [Node.js SDK][ApplicationInsights-Node.js] can be unminified with source maps.
12
+
Application Insights supports the uploading of source maps to your Azure Storage account blob container. You can use source maps to unminify call stacks found on the **End-to-end transaction details** page. You can also use source maps to unminify any exception sent by the [JavaScript SDK][ApplicationInsights-JS] or the [Node.js SDK][ApplicationInsights-Node.js].
14
13
15
-
14
+
16
15
17
-
## Create a new storage account and Blob container
16
+
## Create a new storage account and blob container
18
17
19
18
If you already have an existing storage account or blob container, you can skip this step.
20
19
21
-
1.[Create a new storage account][create storage account]
22
-
2.[Create a blob container][create blob container] inside your storage account. Be sure to set the "Public access level" to `Private`, to ensure that your source maps are not publicly accessible.
20
+
1.[Create a new storage account][create storage account].
21
+
1.[Create a blob container][create blob container] inside your storage account. Set **Public access level** to **Private** to ensure that your source maps aren't publicly accessible.
23
22
24
23
> [!div class="mx-imgBorder"]
25
-
>
24
+
>
26
25
27
-
## Push your source maps to your Blob container
26
+
## Push your source maps to your blob container
28
27
29
-
You should integrate your continuous deployment pipeline with your storage account by configuring it to automatically upload your source maps to the configured Blob container.
28
+
Integrate your continuous deployment pipeline with your storage account by configuring it to automatically upload your source maps to the configured blob container.
30
29
31
-
Source maps can be uploaded to your Blob Storage Container with the same folder structure they were compiled & deployed with. A common use case is to prefix a deployment folder with its version, e.g. `1.2.3/static/js/main.js`. When unminifying via an Azure Blob container called `sourcemaps`, it will try to fetch a source map located at `sourcemaps/1.2.3/static/js/main.js.map`.
30
+
You can upload source maps to your Azure Blob Storage container with the same folder structure they were compiled and deployed with. A common use case is to prefix a deployment folder with its version, for example, `1.2.3/static/js/main.js`. When you unminify via an Azure blob container called `sourcemaps`, the pipeline tries to fetch a source map located at `sourcemaps/1.2.3/static/js/main.js.map`.
32
31
33
32
### Upload source maps via Azure Pipelines (recommended)
34
33
35
-
If you are using Azure Pipelines to continuously build and deploy your application, add an [Azure File Copy][azure file copy] task to your pipeline to automatically upload your source maps.
34
+
If you're using Azure Pipelines to continuously build and deploy your application, add an [Azure file copy][azure file copy] task to your pipeline to automatically upload your source maps.
36
35
37
36
> [!div class="mx-imgBorder"]
38
-
> 
37
+
> 
39
38
40
-
## Configure your Application Insights resource with a Source Map storage account
39
+
## Configure your Application Insights resource with a source map storage account
41
40
42
-
### From the end-to-end transaction details page
41
+
You have two options for configuring your Application Insights resource with a source map storage account.
43
42
44
-
From the end-to-end transaction details tab, you can click on *Unminify* and it will display a prompt to configure if your resource is unconfigured.
43
+
### End-to-end transaction details tab
45
44
46
-
1. In the Portal, view the details of an exception that is minified.
47
-
2. Select *Unminify*.
48
-
3. If your resource has not been configured, a message will appear, prompting you to configure.
45
+
From the **End-to-end transaction details** tab, select **Unminify**. Configure your resource if it's unconfigured.
49
46
50
-
### From the properties page
47
+
1. In the Azure portal, view the details of an exception that's minified.
48
+
1. Select **Unminify**.
49
+
1. If your resource isn't configured, configure it.
51
50
52
-
If you would like to configure or change the storage account or Blob container that is linked to your Application Insights Resource, you can do it by viewing the Application Insights resource's *Properties* tab.
51
+
### Properties tab
53
52
54
-
1. Navigate to the *Properties* tab of your Application Insights resource.
55
-
2. Select *Change source map blob container*.
56
-
3. Select a different Blob container as your source maps container.
57
-
4. Select `Apply`.
53
+
To configure or change the storage account or blob container that's linked to your Application Insights resource:
54
+
55
+
1. Go to the **Properties** tab of your Application Insights resource.
56
+
1. Select **Change source map Blob Container**.
57
+
1. Select a different blob container as your source map container.
58
+
1. Select **Apply**.
58
59
59
60
> [!div class="mx-imgBorder"]
60
-
> 
61
+
> 
61
62
62
63
## Troubleshooting
63
64
64
-
### Required Azure role-based access control (Azure RBAC) settings on your Blob container
65
+
This section offers troubleshooting tips for common issues.
66
+
67
+
### Required Azure role-based access control settings on your blob container
65
68
66
-
Any user on the Portal using this feature must be at least assigned as a [Storage Blob Data Reader][storage blob data reader] to your Blob container. You must assign this role to anyone else that will be using the source maps through this feature.
69
+
Any user on the portal who uses this feature must be assigned at least as a [Storage Blob Data Reader][storage blob data reader] to your blob container. Assign this role to anyone who might use the source maps through this feature.
67
70
68
71
> [!NOTE]
69
-
> Depending on how the container was created, this may not have been automatically assigned to you or your team.
72
+
> Depending on how the container was created, this role might not have been automatically assigned to you or your team.
70
73
71
74
### Source map not found
72
75
73
-
1. Verify that the corresponding source map is uploaded to the correct blob container
74
-
2. Verify that the source map file is named after the JavaScript file it maps to, suffixed with `.map`.
75
-
- For example, `/static/js/main.4e2ca5fa.chunk.js` will search for the blob named `main.4e2ca5fa.chunk.js.map`
76
-
3. Check your browser's console to see if any errors are being logged. Include this in any support ticket.
77
-
78
-
## Next Steps
76
+
1. Verify that the corresponding source map is uploaded to the correct blob container.
77
+
1. Verify that the source map file is named after the JavaScript file it maps to and uses the suffix `.map`:
78
+
- For example, `/static/js/main.4e2ca5fa.chunk.js` searches for the blob named `main.4e2ca5fa.chunk.js.map`.
79
+
1. Check your browser's console to see if any errors were logged. Include this information in any support ticket.
0 commit comments