You are a developer for a company that recently transitioned to using workspace-based Application Insights for a C# .NET web application that runs on Azure. The application has intermittent performance issues. You need to use the Al-powered code analysis feature in Application Insights to help diagnose the problem. What should you do?

To diagnose intermittent performance issues at the code level, the Application Insights Profiler is the appropriate tool. The Profiler captures detailed performance traces for requests in a live production environment. It then performs an analysis to identify the specific methods and lines of code (the "hot path") that consume the most time, directly addressing the need for code analysis to resolve performance problems. The Snapshot Debugger complements this by capturing code and variable states during exceptions, providing a comprehensive diagnostic toolset.

A. Smart detection automatically identifies performance anomalies and failures but does not provide the deep, code-level analysis required to pinpoint the root cause of the slowness.
B. The Application Map is a visualization tool that helps identify bottlenecks between components in a distributed system, but it does not analyze the application's internal code execution paths.
C. Continuous export is a feature for archiving raw telemetry data for long-term storage and offline analysis, not an active diagnostic tool for live performance issues.
E. Availability tests are used to monitor the uptime and basic responsiveness of an application from external locations, not to diagnose internal code-level performance problems.

1. Microsoft Documentation | Azure Monitor | Profile live Azure App Service apps with Application Insights: "Application Insights Profiler... shows you how much time was spent in each method... The profiler helps you identify the 'hot' code path that takes the longest time when it's handling a particular web request." This directly supports using the Profiler for code-level performance diagnosis.

Source: Microsoft Docs, "Profile production applications in Azure with Application Insights", Section: "Enable Profiler".

2. Microsoft Documentation | Azure Monitor | Debug snapshots on exceptions in .NET apps: "When an exception occurs, you can automatically collect a debug snapshot from your live web application. The snapshot shows you the state of the source code and variables at the moment the exception was thrown." This explains the role of the Snapshot Debugger, which is often enabled with the Profiler.

Source: Microsoft Docs, "Debug snapshots on exceptions in .NET apps", Section: "How Snapshot Debugger works".

3. Microsoft Documentation | Azure Monitor | Smart Detection in Application Insights: "Smart Detection automatically warns you of potential performance problems and failure anomalies in your web application. It performs a proactive analysis of the telemetry that your app sends to Application Insights." This confirms that Smart Detection is for anomaly detection, not deep code analysis.

Source: Microsoft Docs, "Smart Detection in Application Insights", Introduction section.