Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The table below describes the table that is displayed in the Association area when you view information on counters.

Table 5- 1 Counter information in the Association area

...

Counters can be examined by drilling down on a specific counter in the counters table area.

Table 2 Main counters:

CounterDescription
Request Counters

Requests Total. Shows the number of requests served by your ASP.NET instance (IIS). These includes all pages processed by the ASP.NET ISAPI filter - not just .aspx, but also .asmx, .axd, .ashx and others.

Requests Failed. Shows the number of requests that failed. A high number might indicate an exception condition is thrown repeatedly in your application.

Other Requests counters. Requests not authorized, Requests authorized, Requests succeeded, Requests Timed Out., Requests Current, Requests Rejected, Requests Queued, Requests Not Found.

Session CountersSession Abandoned, Sessions Timed out, Sessions Total.
Worker Process CountersWorker Process restarts and Worker Process Running counters can be used to detect situations where due to a failure your ASP.NET application restarts frequently.
ASP.NET Error Counters

ASP.NET errors counters can be used to detect errors thrown by your web application and not handled by your code. Explanation about these counters can be found in the SmarTune workspace Advice tabs regarding these counters:

  • Errors Total
  • Errors Unhandled during Execution
  • # of Exceptions thrown
Cache Usage Counters

These counters can be used to detect bad usage of cache by your application. There are several ways to use caching in your ASP.NET application. Explanation about these counters can be found in the SmarTune workspace Advice tabs regarding these counters:

  • Output Cache Hits / Misses / Entries
  • Cache API Hits / Misses / Entries
  • Cache Total Hits / Misses / Entries

...

The Used Memory (Avg) counter shows average memory consumed by your .NET application. Use this graph to detect patterns of increasing memory usage, possibly caused by a memory leak in your code.

 

...

.

...