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
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/javascript.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,8 @@ description: Get page view and session counts, web client data, Single Page Appl
4
4
ms.service: azure-monitor
5
5
ms.subservice: application-insights
6
6
ms.topic: conceptual
7
-
author: mrbullwinkle
8
-
ms.author: mbullwin
7
+
author: Dawgfan
8
+
ms.author: mmcc
9
9
ms.date: 09/20/2019
10
10
11
11
---
@@ -16,7 +16,7 @@ Find out about the performance and usage of your web page or app. If you add [Ap
16
16
17
17
Application Insights can be used with any web pages - you just add a short piece of JavaScript. If your web service is [Java](java-get-started.md) or [ASP.NET](asp-net.md), you can use the server-side SDKs in conjunction with the client-side JavaScript SDK to get an end-to-end understanding of your app's performance.
18
18
19
-
## Adding the Javascript SDK
19
+
## Adding the JavaScript SDK
20
20
21
21
1. First you need an Application Insights resource. If you don't already have a resource and instrumentation key, follow the [create a new resource instructions](create-new-resource.md).
22
22
2. Copy the instrumentation key from the resource where you want your JavaScript telemetry to be sent.
@@ -25,7 +25,10 @@ Application Insights can be used with any web pages - you just add a short piece
25
25
*[JavaScript Snippet](#snippet-based-setup)
26
26
27
27
> [!IMPORTANT]
28
-
> You only need to use one of the methods below for adding the Application Insights JavaScript SDK to your application. If you use the npm based setup, don't use the snippet based setup. The same goes for the reverse scenario when using the snippet based approach, don't also use the npm based setup.
28
+
> > Only use one method to add the JavaScript SDK to your application. If you use the NPM Setup, don't use the Snippet and vice versa.
29
+
30
+
> [!NOTE]
31
+
> NPM Setup installs the JavaScript SDK as a dependency to your project, enabling IntelliSense, whereas the Snippet fetches the SDK at runtime. Both support the same features. However, developers who desire more custom events and configuration generally opt for NPM Setup whereas users looking for quick enablement of out-of-the-box web analytics opt for the Snippet.
29
32
30
33
### npm based setup
31
34
@@ -205,7 +208,7 @@ This version comes with the bare minimum number of features and functionalities
205
208
206
209
## Examples
207
210
208
-
For runnable examples, see [Application Insights Javascript SDK Samples](https://github.com/topics/applicationinsights-js-demo)
211
+
For runnable examples, see [Application Insights JavaScript SDK Samples](https://github.com/topics/applicationinsights-js-demo)
209
212
210
213
## Upgrading from the old Version of Application Insights
211
214
@@ -258,4 +261,3 @@ The Application Insights JavaScript SDK is open-source to view the source code o
258
261
*[Track usage](usage-overview.md)
259
262
*[Custom events and metrics](api-custom-events-metrics.md)
0 commit comments