Issue Detection

Basic Issues

• Performance hotspot – detects methods that consume a significant portion of total execution time. Threshold: execution time in milliseconds.

• UI freeze – detects intervals where the UI thread was unresponsive. Threshold: freeze duration in milliseconds.

• High GC activity – detects intervals where a large percentage of total execution time was spent on garbage collection. Threshold: GC time percentage.

Database Issues

• Slow DB command – detects database commands whose execution time exceeds the threshold. Threshold: command execution time in milliseconds.

• Excessive DB commands – detects repeated execution of the same database command (for example, an N+1 query pattern). Threshold: number of commands.

• Large DB result set – detects database commands returning more records than the defined threshold. Threshold: number of records.

• Excessive DB connections – detects code that opens too many simultaneous database connections. Threshold: number of connections.

ASP.NET Core Issues

• Slow MVC action – detects ASP.NET Core controller actions that exceed the time threshold. Threshold: action execution time in milliseconds.

• Slow Razor page handler – detects long-running Razor page handler methods (for example, OnGet or OnPost). Threshold: handler execution time in milliseconds.

• Slow Razor view component – detects slow Invoke() or InvokeAsync() methods in Razor view components. Threshold: method execution time in milliseconds.

Auto-disable issue detection

• Auto-disable ASP inspections that affect performance – If there are too many ASP.NET Core events in the system, it may take some time for Monitoring to process them. If this option is enabled, Monitoring will automatically turn off ASP inspections that affect performance. Note that the inspections will be disabled not for the current but for all future application runs.