microsoft.visualstudio.applicationinsights.dll

Company
Microsoft Corporation
Description

Application Insights Getting Started Package

Version
8.4.1118.2
Architecture
32 bit
Threat Score
0 %
Original size
2406.7 Kb
Download size
842.5 Kb
MD5
01b9dc20acb0edfa57a59899f85ffffb
SHA1
41eb71812fc688d5c7fbb6e54302c998bb8a9c76
SHA256
3c40b9034994feff06edc6211606fb82e21694dba2af1d69df0218a6646f5e80
'Failed to enable exception collection. 

>

Configure Application Insights and enable the logging adapters

>

Run your application to start seeing data in the Azure Portal.

*Please select a valid start date and time.

1Enable richer analytics with Application Insights

2Enable richer analytics with _Application Insights

5Configure Application Insights and enable {0} adapter

6Enable richer analysis over your app's telemetry data.

=Enable symbolicated crash collection for meaningful analysis.

Enable Application Insights

Enable Crash Analytics...

Enable exception collection

Enable trace collection

Enable {0} trace collection

IEnable to search and analyze unhandled exceptions in your controllers. This will modify FilterConfig.cs. 

IEnable to search and analyze {0} traces. This will add {1} NuGet package.

LThere was an error while retrieving the Instrumentation Key from the server.

Resource group name must start with a letter and end with an alphanumeric character, and can only include the following special characters: numbers, underscores, hyphens, and periods.

Start Time

Start a debug session of a compatible Application Insights project to see data here.

This will fetch telemetry within the time range and present the results as a filterable time series histogram for further analysis. Common choices for 'Group By' include 'request.performanceBucket' for performance analysis and 'request.responseCode' for error analysis.

This will update the Y-axis dimension and allow you to analyze trends over time with respect to the items in this dimension. Choosing an appropriate dimension for the analysis you are performing can help simplify the exploration process. For instance, you can choose request.performanceBucket for performance analysis and request.ResponseCode for error analysis.

UWe're sorry, but something went wrong. Please restart Visual Studio to show exception

View error message

We could not detect that you added AiErrorHandleAttribute in FilterConfig or find AiHandleErrorAttribute in your project. Enable exception collection to fix it.

We were unable to find a build for the current configuration. Once you build your project, we will be able to zip and upload the build folder.

_No exceptions were found in your app over the last 24 hours. Enable exception collection in the

{You're almost there. Connect your project to Application Insights for telemetry and performance monitoring. Start for free.

|Wading through large amounts of telemetry can be daunting. We recommend that you start with one these common analysis types.

Last update: 04/10/2025