Uncaught exceptions in your app, including information on
Stack trace
Exception details and message accompanying the error
Line & column number of error
URL where error was raised
Network Dependency Requests made by your app XML Http Request (XHR) and Fetch (fetch collection is disabled by default) requests, include information on:
Url of dependency source
Command & Method used to request the dependency
Duration of the request
Result code and success status of the request
ID (if any) of user making the request
Correlation context (if any) where request is made
User information (for example, Location, network, IP)
Device information (for example, Browser, OS, version, language, model)
Session information
Note
For some applications, such as single-page applications (SPAs), the duration may not be recorded and will default to 0.
How many Application Insights resources should I deploy?
To understand the number of Application Insights resources required to cover your application or components across environments, see the Application Insights deployment planning guide.
How can I manage Application Insights resources with PowerShell?
How long does it take for telemetry to be collected?
Most Application Insights data has a latency of under 5 minutes. Some data can take longer, which is typical for larger log files. See the Application Insights service-level agreement.
How does Application Insights handle data collection, retention, storage, and privacy?
Collection
Application Insights collects telemetry about your app, including web server telemetry, web page telemetry, and performance counters. This data can be used to monitor your app's performance, health, and usage. You can select the location when you create a new Application Insights resource.
Retention and Storage
Data is sent to an Application Insights Log Analytics workspace. You can choose the retention period for raw data, from 30 to 730 days. Aggregated data is retained for 90 days, and debug snapshots are retained for 15 days.
Privacy
Application Insights doesn't handle sensitive data by default. We recommend you don't put sensitive data in URLs as plain text and ensure your custom code doesn't collect personal or other sensitive details. During development and testing, check the sent data in your IDE and browser's debugging output windows.
Application Insights is billed through the Log Analytics workspace into which its log data ingested. The default Pay-as-you-go Log Analytics pricing tier includes 5 GB per month of free data allowance per billing account. Learn more about Azure Monitor logs pricing options.
Are there data transfer charges between an Azure web app and Application Insights?
If your Azure web app is hosted in a datacenter where there's an Application Insights collection endpoint, there's no charge.
If there's no collection endpoint in your host datacenter, your app's telemetry incurs Azure outgoing charges.
This answer depends on the distribution of our endpoints, not on where your Application Insights resource is hosted.
Do I incur network costs if my Application Insights resource is monitoring an Azure resource (that is, telemetry producer) in a different region?
Yes, you can incur more network costs, which vary depending on the region the telemetry is coming from and where it's going.
Refer to Azure bandwidth pricing for details.
What TLS versions does Application Insights support
Important
On 1 March 2025, in alignment with the Azure wide legacy TLS retirement, TLS 1.0/1.1 protocol versions and the listed TLS 1.2/1.3 legacy Cipher suites and Elliptical curves will be retired for Application Insights.
To provide best-in-class encryption, Application Insights uses Transport Layer Security (TLS) 1.2 and 1.3 as the encryption mechanisms of choice.
Build end-to-end solutions in Microsoft Azure to create Azure Functions, implement and manage web apps, develop solutions utilizing Azure storage, and more.