- System Monitor Overview
- The Big Three
- Web Service Counters
- ASP.NET Counters
- Conclusion
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Web Service Counters
To bring up the Web Service counters, right-click the right pane of the SM console and choose Add Counters. Next, select the Web Service Performance Object (WSPO) from the object list. The counters I'll discuss appear in the left column, as shown in Figure 2.
)
Figure
2 Web Service counter collection.
As you can see, the WSPO object has a large set of counters, which can be expected because we're talking statistics for connections, requests, and bandwidth pertaining to our Web Service (IIS 6.0) and the Web sites managed by the service.
The Current blocked bandwidth bytes counter was not seen before in SM with previous versions of NT. This counter will tell us how many current bytes are being blocked, based on bandwidth throttling that has been applied to one or more of the Web sites hosted on our server.
NOTE
Bandwidth throttling is a term used to refer to how much bandwidth a Web site is allowed to use. For one or more Web sites, administrators can enable bandwidth throttling and set a value that will determine the site's limited network use in terms of bandwidth.
There are other counters that also allow us to monitor bandwidth throttling, such as the Current Blocked Async I/O Requests counter. It will tell us how many requests are being blocked due to a site's bandwidth constraints. If we determine that a site needs more bandwidth because of more traffic on a consistent basis, we can look at the Current blocked bandwidth bytes counter to tell about how much more. If you're into bandwidth crunching for your sites, this counter is a nice addition to SM.
If you scroll down to the Total counters, there are four new ones not seen in previous versions that deal with bandwidth: Total Blocked Bandwidth Bytes, Total Bytes Received, Total Bytes Sent, and Total Bytes Transferred. These counters display the cumulative total bytes since service uptime. Helpful if we want an overall picture of how much incoming and outgoing bandwidth usage any one of our sites is using. If you're a Web hosting service and charge for bandwidth usage, you can use these counters to determine how much to charge a client.
In my opinion, one of the most useful counters for the Web Service object is the Total Method Requests counter. It simply tells us how many requests have been made for a Web site since IIS startup. Based on this value, we can tell which sites are busy. Knowing this, we can pull some of the other counters to determine whether performance tweaking is needed.