Microsoft Azure Monitor Application Insights JavaScript SDK configuration

The Azure Application Insights JavaScript SDK provides configuration for tracking, monitoring, and debugging your web applications.

SDK configuration

These configuration fields are optional and default to false unless otherwise stated. The following sections group the fields by purpose.

For instructions on how to add SDK configuration, see Add SDK configuration.

Cookies and session storage

Use disableCookiesUsage to disable cookies entirely, cookieCfg for full instance-based cookie configuration, cookieDomain and cookiePath to scope cookies across subdomains or application gateways, and namePrefix, sessionCookiePostfix, and userCookiePostfix to customize cookie and localStorage names.

Ajax and Fetch tracking

Ajax and Fetch auto-collection is grouped into five capability areas: on/off toggles (disableAjaxTracking, disableFetchTracking, disableXhr), request and response header capture (enableRequestHeaderTracking, enableResponseHeaderTracking, ignoreHeaders, customHeaders), URL-based filtering (excludeRequestFromAutoTrackingPatterns), extra window.performance lookups (enableAjaxPerfTracking, ajaxPerfLookupDelay, maxAjaxPerfLookupAttempts, enableAjaxErrorStatusText), and per-page volume control and per-call enrichment (maxAjaxCallsPerView, addRequestContext).

Auto-collection toggles

Use these fields to enable or disable automatic collection of Ajax and Fetch requests and to choose the transport (XHR, Fetch, or Beacon).

Header tracking

Use these fields to include AJAX and Fetch request or response headers in dependency telemetry, provide extra headers on custom endpoints, or filter sensitive headers out of the log.

URL filtering

Use this field to exclude specific request URLs from automatic Ajax and Fetch tracking.

Performance lookups

Use these fields to include extra window.performance timings on Ajax dependency telemetry, tune the lookup delay and retry count, and include response error text on failed AJAX requests.

Volume control and enrichment

Use maxAjaxCallsPerView to cap per-page-view Ajax collection, and addRequestContext to enrich dependency telemetry with a callback at the start of each API call.

Distributed tracing and correlation

Use distributedTracingMode to select W3C, AI, or AI_AND_W3C header format. Use disableCorrelationHeaders to turn correlation off entirely. Use enableCorsCorrelation to inject correlation headers on cross-origin requests. Use appId to set a fixed correlation identity. Use correlationHeaderDomains, correlationHeaderExcludedDomains, and correlationHeaderExcludePatterns to allow-list or block-list specific target domains or URL patterns.

Page views and route tracking

Use enableAutoRouteTracking to track SPA route changes. Use autoTrackPageVisitTime to record time-on-page for the previous view. Use isBrowserLinkTrackingEnabled to track Browser Link requests. Use overridePageViewDuration to compute page view duration from trackPageView calls instead of the navigation timing API.

Exception tracking

Use disableExceptionTracking to opt out of automatic exception collection, and enableUnhandledPromiseRejectionTracking to include unhandled promise rejections as JavaScript errors.

Sampling, batching, and storage

Use samplingPercentage to set the fixed sampling rate, maxBatchInterval and maxBatchSizeInBytes to tune batch send behavior, enableSessionStorageBuffer and isStorageUseDisabled to control whether the SDK persists unsent telemetry in session or local storage, eventsLimitInMem to cap the in-memory buffer, isRetryDisabled to disable retries on transient failures, disableFlushOnBeforeUnload to skip the flush on page unload, and disableTelemetry as a global off switch.

Logging and debugging

Use loggingLevelConsole and loggingLevelTelemetry to route internal SDK errors to the console or to telemetry. Use enableDebug to throw internal errors as exceptions during development. Use diagnosticLogInterval to tune the internal log poller. Use disableDataLossAnalysis to skip startup buffer checks. Use disableIkeyDeprecationMessage to suppress the instrumentation key deprecation notice.

Performance manager

Use enablePerfMgr to emit local perfEvents from instrumented code paths. Use createPerfMgr to supply a custom IPerfManager factory. Use perfEvtsSendAll to control whether every perfEvent fires or only parent events.

Identifiers and session lifetime

Use accountId to group users into accounts, idLength to set the generated random ID length, sessionExpirationMs for maximum session duration, and sessionRenewalMs for the inactivity timeout that ends a session.

Other settings

Use featureOptIn to opt into preview features, throttleMgrCfg to configure throttling, disableInstrumentationKeyValidation to bypass ingestion key checks, convertUndefined to substitute a default value for undefined fields, and sdkExtension to prefix the ai.internal.sdkVersion tag for downstream SDK extensions.

Distributed tracing

Modern cloud and microservices architectures have enabled simple, independently deployable services that reduce costs while increasing availability and throughput. However, it has made overall systems more difficult to reason about and debug. Distributed tracing solves this problem by providing a performance profiler that works like call stacks for cloud and microservices architectures.

Azure Monitor provides two experiences for consuming distributed trace data: the transaction diagnostics view for a single transaction/request and the application map view to show how systems interact.

Application Insights can monitor each component separately and detect which component is responsible for failures or performance degradation by using distributed telemetry correlation. This article explains the data model, context-propagation techniques, protocols, and implementation of correlation tactics on different languages and platforms used by Application Insights.

Enable distributed tracing via Application Insights through autoinstrumentation or SDKs

Supported Azure Monitor OpenTelemetry instrumentation and the JavaScript SDK emit distributed tracing data for common frameworks and libraries.

With supported instrumentation configured, tracing information is automatically collected for common frameworks, libraries, and technologies.

Any technology can also be tracked manually by creating custom spans.

Data model for telemetry correlation

Application Insights defines a data model for distributed telemetry correlation. To associate telemetry with a logical operation, every telemetry item has a context field called operation_Id. Every telemetry item in the distributed trace shares this identifier. So even if you lose telemetry from a single layer, you can still associate telemetry reported by other components.

A distributed logical operation typically consists of a set of smaller operations that are requests processed by one of the components. Request telemetry defines these operations. Every request telemetry item has its own id that identifies it uniquely and globally. And all telemetry items (such as traces and exceptions) that are associated with the request should set the operation_parentId to the value of the request id.

Dependency telemetry represents every outgoing operation, such as an HTTP call to another component. It also defines its own id that's globally unique. Request telemetry, initiated by this dependency call, uses this id as its operation_parentId.

You can build a view of the distributed logical operation by using operation_Id, operation_parentId, and request.id with dependency.id. These fields also define the causality order of telemetry calls.

In a microservices environment, traces from components can go to different storage items. Every component can have its own connection string in Application Insights. To get telemetry for the logical operation, Application Insights queries data from every storage item.

When the number of storage items is large, you need a hint about where to look next. The Application Insights data model defines two fields to solve this problem: request.source and dependency.target. The first field identifies the component that initiated the dependency request. The second field identifies which component returned the response of the dependency call.

For information on querying from multiple disparate instances, see Query data across Log Analytics workspaces, applications, and resources in Azure Monitor.

Example

Let's look at an example. An application called Stock Prices shows the current market price of a stock by using an external API called Stock. The Stock Prices application has a page called Stock page that the client web browser opens by using GET /Home/Stock. The application queries the Stock API by using the HTTP call GET /api/stock/value.

You can analyze the resulting telemetry by running a query:

(requests | union dependencies | union pageViews)
| where operation_Id == "STYz"
| project timestamp, itemType, name, id, operation_ParentId, operation_Id

In the results, all telemetry items share the root operation_Id. When an Ajax call is made from the page, a new unique ID (qJSXU) is assigned to the dependency telemetry, and the ID of the pageView is used as operation_ParentId. The server request then uses the Ajax ID as operation_ParentId.

When the call GET /api/stock/value is made to an external service, you need to know the identity of that server so you can set the dependency.target field appropriately. When the external service doesn't support monitoring, target is set to the host name of the service. An example is stock-prices-api.com. But if the service identifies itself by returning a predefined HTTP header, target contains the service identity that allows Application Insights to build a distributed trace by querying telemetry from that service.

Correlation headers using W3C TraceContext

Application Insights is transitioning to W3C Trace-Context, which defines:

• traceparent: Carries the globally unique operation ID and unique identifier of the call.
• tracestate: Carries system-specific tracing context.

Supported instrumentation uses the W3C Trace Context protocol for distributed tracing.

The correlation HTTP protocol, also called Request-Id, is being deprecated. This protocol defines two headers:

• Request-Id: Carries the globally unique ID of the call.
• Correlation-Context: Carries the name-value pairs collection of the distributed trace properties.

Application Insights also uses correlation context to populate fields such as dependency.target and request.source when that context is available.

The W3C Trace-Context and Application Insights data models map in the following way:

For more information, see Application Insights telemetry data model.

Enable W3C distributed tracing support

This feature is enabled by default for JavaScript, and the headers are automatically included when the hosting page domain is the same as the domain the requests are sent to (for example, the hosting page is example.com and the Ajax requests are sent to example.com). To change the distributed tracing mode, use the distributedTracingMode configuration field. The default value, AI_AND_W3C, provides backward compatibility with any legacy services instrumented by Application Insights.

• npm-based setup

  Add the following configuration:

    distributedTracingMode: DistributedTracingModes.W3C
  

• JavaScript (Web) SDK Loader Script-based setup

  Add the following configuration:

      distributedTracingMode: 2 // DistributedTracingModes.W3C
  

If the XMLHttpRequest or Fetch Ajax requests go to a different domain host, including subdomains, the correlation headers aren't included by default. To enable this feature, set the enableCorsCorrelation configuration field to true. If you set enableCorsCorrelation to true, all XMLHttpRequest and Fetch Ajax requests include the correlation headers. As a result, if the application on the server that the request calls doesn't support the traceparent header, the request might fail. This failure depends on whether the browser and version can validate the request based on which headers the server accepts. You can use the correlationHeaderExcludedDomains configuration field to exclude the server's domain from cross-component correlation header injection. For example, you can use correlationHeaderExcludedDomains: ['*.auth0.com'] to exclude correlation headers from requests sent to the Auth0 identity provider.

Filter and preprocess telemetry

For JavaScript web applications, use telemetry initializers to filter, modify, or enrich telemetry before it's sent.

• Return false from an initializer to drop a telemetry item before it is sent.
• Add or modify fields on the telemetry item to enrich telemetry with values that are useful for filtering and analysis.
• Use SDK sampling configuration to reduce telemetry volume when you need statistical sampling instead of explicit filtering.

JavaScript web applications

To filter telemetry from JavaScript web applications, use ITelemetryInitializer.

1. Create a telemetry initializer callback function. The callback function takes ITelemetryItem as a parameter, which is the event that's being processed. If the callback returns false, the telemetry item is filtered out.

   var filteringFunction = (envelope) => {
     if (envelope.data.someField === 'tobefilteredout') {
       return false;
     }
     return true;
   };
   

2. Add your telemetry initializer callback:

   appInsights.addTelemetryInitializer(filteringFunction);
   

JavaScript telemetry initializers

Telemetry initializers run before a JavaScript telemetry item is sent. Use them to add, modify, or drop browser telemetry. Returning false from an initializer drops the item.

Use telemetry initializers for targeted enrichment or filtering. Use sampling when you need volume reduction without explicitly excluding specific telemetry.

JavaScript telemetry initializers

Insert a JavaScript telemetry initializer, if needed. For more information on the telemetry initializers for the Application Insights JavaScript SDK, see Telemetry initializers.

<script type="text/javascript">
!(function (cfg){function e(){cfg.onInit&&cfg.onInit(n)}var x,w,D,t,E,n,C=window,O=document,b=C.location,q="script",I="ingestionendpoint",L="disableExceptionTracking",j="ai.device.";"instrumentationKey"[x="toLowerCase"](),w="crossOrigin",D="POST",t="appInsightsSDK",E=cfg.name||"appInsights",(cfg.name||C[t])&&(C[t]=E),n=C[E]||function(g){var f=!1,m=!1,h={initialize:!0,queue:[],sv:"8",version:2,config:g};function v(e,t){var n={},i="Browser";function a(e){e=""+e;return 1===e.length?"0"+e:e}return n[j+"id"]=i[x](),n[j+"type"]=i,n["ai.operation.name"]=b&&b.pathname||"_unknown_",n["ai.internal.sdkVersion"]="javascript:snippet_"+(h.sv||h.version),{time:(i=new Date).getUTCFullYear()+"-"+a(1+i.getUTCMonth())+"-"+a(i.getUTCDate())+"T"+a(i.getUTCHours())+":"+a(i.getUTCMinutes())+":"+a(i.getUTCSeconds())+"."+(i.getUTCMilliseconds()/1e3).toFixed(3).slice(2,5)+"Z",iKey:e,name:"Microsoft.ApplicationInsights."+e.replace(/-/g,"")+"."+t,sampleRate:100,tags:n,data:{baseData:{ver:2}},ver:undefined,seq:"1",aiDataContract:undefined}}var n,i,t,a,y=-1,T=0,S=["js.monitor.azure.com","js.cdn.applicationinsights.io","js.cdn.monitor.azure.com","js0.cdn.applicationinsights.io","js0.cdn.monitor.azure.com","js2.cdn.applicationinsights.io","js2.cdn.monitor.azure.com","az416426.vo.msecnd.net"],o=g.url||cfg.src,r=function(){return s(o,null)};function s(d,t){if((n=navigator)&&(~(n=(n.userAgent||"").toLowerCase()).indexOf("msie")||~n.indexOf("trident/"))&&~d.indexOf("ai.3")&&(d=d.replace(/(\/)(ai\.3\.)([^\d]*)$/,function(e,t,n){return t+"ai.2"+n})),!1!==cfg.cr)for(var e=0;e<S.length;e++)if(0<d.indexOf(S[e])){y=e;break}var n,i=function(e){var a,t,n,i,o,r,s,c,u,l;h.queue=[],m||(0<=y&&T+1<S.length?(a=(y+T+1)%S.length,p(d.replace(/^(.*\/\/)([\w\.]*)(\/.*)$/,function(e,t,n,i){return t+S[a]+i})),T+=1):(f=m=!0,s=d,!0!==cfg.dle&&(c=(t=function(){var e,t={},n=g.connectionString;if(n)for(var i=n.split(";"),a=0;a<i.length;a++){var o=i[a].split("=");2===o.length&&(t[o[0][x]()]=o[1])}return t[I]||(e=(n=t.endpointsuffix)?t.location:null,t[I]="https://"+(e?e+".":"")+"dc."+(n||"services.visualstudio.com")),t}()).instrumentationkey||g.instrumentationKey||"",t=(t=(t=t[I])&&"/"===t.slice(-1)?t.slice(0,-1):t)?t+"/v2/track":g.endpointUrl,t=g.userOverrideEndpointUrl||t,(n=[]).push((i="SDK LOAD Failure: Failed to load Application Insights SDK script (See stack for details)",o=s,u=t,(l=(r=v(c,"Exception")).data).baseType="ExceptionData",l.baseData.exceptions=[{typeName:"SDKLoadFailed",message:i.replace(/\./g,"-"),hasFullStack:!1,stack:i+"\nSnippet failed to load ["+o+"] -- Telemetry is disabled\nHelp Link: https://go.microsoft.com/fwlink/?linkid=2128109\nHost: "+(b&&b.pathname||"_unknown_")+"\nEndpoint: "+u,parsedStack:[]}],r)),n.push((l=s,i=t,(u=(o=v(c,"Message")).data).baseType="MessageData",(r=u.baseData).message='AI (Internal): 99 message:"'+("SDK LOAD Failure: Failed to load Application Insights SDK script (See stack for details) ("+l+")").replace(/\"/g,"")+'"',r.properties={endpoint:i},o)),s=n,c=t,JSON&&((u=C.fetch)&&!cfg.useXhr?u(c,{method:D,body:JSON.stringify(s),mode:"cors"}):XMLHttpRequest&&((l=new XMLHttpRequest).open(D,c),l.setRequestHeader("Content-type","application/json"),l.send(JSON.stringify(s)))))))},a=function(e,t){m||setTimeout(function(){!t&&h.core||i()},500),f=!1},p=function(e){var n=O.createElement(q),e=(n.src=e,t&&(n.integrity=t),n.setAttribute("data-ai-name",E),cfg[w]);return!e&&""!==e||"undefined"==n[w]||(n[w]=e),n.onload=a,n.onerror=i,n.onreadystatechange=function(e,t){"loaded"!==n.readyState&&"complete"!==n.readyState||a(0,t)},cfg.ld&&cfg.ld<0?O.getElementsByTagName("head")[0].appendChild(n):setTimeout(function(){O.getElementsByTagName(q)[0].parentNode.appendChild(n)},cfg.ld||0),n};p(d)}cfg.sri&&(n=o.match(/^((http[s]?:\/\/.*\/)\w+(\.\d+){1,5})\.(([\w]+\.){0,2}js)$/))&&6===n.length?(d="".concat(n[1],".integrity.json"),i="@".concat(n[4]),l=window.fetch,t=function(e){if(!e.ext||!e.ext[i]||!e.ext[i].file)throw Error("Error Loading JSON response");var t=e.ext[i].integrity||null;s(o=n[2]+e.ext[i].file,t)},l&&!cfg.useXhr?l(d,{method:"GET",mode:"cors"}).then(function(e){return e.json()["catch"](function(){return{}})}).then(t)["catch"](r):XMLHttpRequest&&((a=new XMLHttpRequest).open("GET",d),a.onreadystatechange=function(){if(a.readyState===XMLHttpRequest.DONE)if(200===a.status)try{t(JSON.parse(a.responseText))}catch(e){r()}else r()},a.send())):o&&r();try{h.cookie=O.cookie}catch(k){}function e(e){for(;e.length;)!function(t){h[t]=function(){var e=arguments;f||h.queue.push(function(){h[t].apply(h,e)})}}(e.pop())}var c,u,l="track",d="TrackPage",p="TrackEvent",l=(e([l+"Event",l+"PageView",l+"Exception",l+"Trace",l+"DependencyData",l+"Metric",l+"PageViewPerformance","start"+d,"stop"+d,"start"+p,"stop"+p,"addTelemetryInitializer","setAuthenticatedUserContext","clearAuthenticatedUserContext","flush"]),h.SeverityLevel={Verbose:0,Information:1,Warning:2,Error:3,Critical:4},(g.extensionConfig||{}).ApplicationInsightsAnalytics||{});return!0!==g[L]&&!0!==l[L]&&(e(["_"+(c="onerror")]),u=C[c],C[c]=function(e,t,n,i,a){var o=u&&u(e,t,n,i,a);return!0!==o&&h["_"+c]({message:e,url:t,lineNumber:n,columnNumber:i,error:a,evt:C.event}),o},g.autoExceptionInstrumented=!0),h}(cfg.cfg),(C[E]=n).queue&&0===n.queue.length?(n.queue.push(e),n.trackPageView({})):e();})({
src: "https://js.monitor.azure.com/scripts/b/ai.3.gbl.min.js",
crossOrigin: "anonymous", // When supplied this will add the provided value as the cross origin attribute on the script tag
onInit: function (sdk) {
    sdk.addTelemetryInitializer(function (envelope) {
    envelope.data = envelope.data || {};
    envelope.data.someField = 'This item passed through my telemetry initializer';
    });
}, // Once the application insights instance has loaded and initialized this method will be called
// sri: false, // Custom optional value to specify whether fetching the snippet from integrity file and do integrity check
cfg: { // Application Insights Configuration
    connectionString: "YOUR_CONNECTION_STRING"
}});
</script>

import { ApplicationInsights } from '@microsoft/applicationinsights-web'

const appInsights = new ApplicationInsights({ config: {
  connectionString: 'YOUR_CONNECTION_STRING'
  /* ...Other Configuration Options... */
} });
appInsights.loadAppInsights();
// To insert a telemetry initializer, uncomment the following code.
/** var telemetryInitializer = (envelope) => { envelope.data = envelope.data || {}; envelope.data.someField = 'This item passed through my telemetry initializer';
 };
appInsights.addTelemetryInitializer(telemetryInitializer); **/
appInsights.trackPageView();

For a summary of the noncustom properties available on the telemetry item, see Application Insights Export Data Model.

You can add as many initializers as you like. They're called in the order that you add them.

Add a cloud role name and cloud role instance

Use a telemetry initializer to set the ai.cloud.role and ai.cloud.roleInstance tags. These tags define how your component appears in the Application Map in Azure Monitor.

appInsights.queue.push(() => {
appInsights.addTelemetryInitializer((envelope) => {
  envelope.tags["ai.cloud.role"] = "your role name";
  envelope.tags["ai.cloud.roleInstance"] = "your role instance";
});
});

Cookie management

Starting from version 2.6.0, the Azure Application Insights JavaScript SDK provides instance-based cookie management that you can disable and re-enable after initialization.

If you disable cookies during initialization by using the disableCookiesUsage or cookieCfg.enabled configurations, you can re-enable them by using the setEnabled function of the ICookieMgr object.

The instance-based cookie management replaces the previous CoreUtils global functions of disableCookies(), setCookie(), getCookie(), and deleteCookie().

To take advantage of the tree-shaking enhancements introduced in version 2.6.0, stop using the global functions.

Cookie configuration

ICookieMgrConfig is a cookie configuration for instance-based cookie management added in version 2.6.0. The options it provides allow you to enable or disable the use of cookies by the SDK. You can also set custom cookie domains and paths, and customize the functions for fetching, setting, and deleting cookies.

The following table defines the ICookieMgrConfig options.

Source map

Source map support helps you debug minified JavaScript code by unminifying the minified call stack of your exception telemetry.

Link to Blob Storage account

Application Insights supports uploading source maps to your Azure Storage account blob container. 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 or the Node.js SDK.

Create a new storage account and blob container

If you already have an existing storage account or blob container, you can skip this step.

1. Create a new storage account.

2. Create a blob container inside your storage account. Set Public access level to Private to ensure that your source maps aren't publicly accessible.

   

Push your source maps to your blob container

Integrate your continuous deployment pipeline with your storage account by configuring it to automatically upload your source maps to the configured blob container.

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.

Upload source maps via Azure Pipelines (recommended)

If you're using Azure Pipelines to continuously build and deploy your application, add an Azure file copy task to your pipeline to automatically upload your source maps.

Configure your Application Insights resource with a source map storage account

You have two options for configuring your Application Insights resource with a source map storage account.

End-to-end transaction details tab

From the End-to-end transaction details tab, select Unminify. Configure your resource if it's unconfigured.

1. In the Azure portal, view the details of an exception that's minified.
2. Select Unminify.
3. If your resource isn't configured, configure it.

Properties tab

To configure or change the storage account or blob container that's linked to your Application Insights resource:

1. Go to the Properties tab of your Application Insights resource.

2. Select Change source map Blob Container.

3. Select a different blob container as your source map container.

4. Select Apply.

   

View the unminified call stack

To view the unminified call stack, select an Exception Telemetry item in the Azure portal, find the source maps that match the call stack, and drag and drop the source maps onto the call stack in the Azure portal. The source map must have the same name as the source file of a stack frame, but with a map extension.

If you experience issues that involve source map support for JavaScript applications, see Troubleshoot source map support for JavaScript applications.

Tree shaking

Tree shaking removes unused code from the final JavaScript bundle.

To take advantage of tree shaking, import only the necessary components of the SDK into your code. By doing this, you exclude unused code from the final bundle, which reduces its size and improves performance.

Tree shaking enhancements and recommendations

In version 2.6.0, the SDK deprecated and removed the internal usage of these static helper classes to improve support for tree-shaking algorithms. This change lets npm packages safely drop unused code.

• CoreUtils
• EventHelper
• Util
• UrlHelper
• DateTimeUtils
• ConnectionStringParser

The functions are now exported as top-level roots from the modules, making it easier to refactor your code for better tree shaking.

The static classes are now const objects that reference the new exported functions.

Tree shaking deprecated functions and replacements

This section applies only if you're using the deprecated functions and want to optimize package size. To reduce size and support all versions of Internet Explorer, use the replacement functions.

Service notifications

The SDK includes service notifications that provide actionable recommendations to help ensure your telemetry flows uninterrupted to Application Insights. You see the notifications as an exception message within Application Insights. The SDK ensures notifications are relevant to you based on your SDK settings, and it adjusts the verbosity based on the urgency of the recommendation. Keep service notifications on, but you can opt out via the featureOptIn configuration.

Currently, no active notifications are being sent.

The JavaScript SDK manages service notifications and regularly polls a public JSON file to control and update these notifications. To disable the polling made by the JavaScript SDK, disable the featureOptIn mode.

Troubleshooting

See the dedicated troubleshooting article.

Next steps

• To review frequently asked questions (FAQ), see JavaScript SDK configuration FAQ.
• Track usage.
• Azure file copy task.
• Azure Monitor data types reference and SDK code for JavaScript SDK.