Performance Counters to trace for troubleshooting performance issue

I've been involve in some performance testing for a typical MOSS implementation lately. Although I have done these test many times on different projects, but I find that each performance test is unique, depending on the test objective, environment, the test subject (portal pages and components). Still, one thing that remain quite consistent is the performance counter to monitor. The following performance counter were used for the most recent performance test. I've included additional ASP.NET Application cache counters, as I want to verify whether the MOSS cache profile is working properly.

Counter Object	Counter	WFE	Index	SQL	Client	Remark
Processor (_Total)	% Processor Time	Y	Y	Y	Y	Not more than 70%
Memory	Available Bytes Pages/Sec	Y	Y	Y	Y
Physical Disk	% Disk Time Avg. Disk Queue Length	Y		Y
Network	Bytes Sent/Sec Bytes Received/Sec Bytes Total/Sec	Y	Y	Y	Y	http://technet.microsoft.com/en-us/library/aa996224.aspx Bytes Total/Sec for 1000mbps NIC should not go over 70MB/s Bytes Total/Sec for 100mbps NIC should not go over 7MB/s
ASP.NET Applications	Request Total Requests/sec Request Execution Time Requests Succeeded Request Rejected Requests Timed Out Requests Not Found Requests Not Authorized Output Cache Hits Output Cache Misses	Y				Refer to http://msdn.microsoft.com/en-us/library/fxk122b4.aspx for description of ASP.NET performance counters.

I will include the SQL server performance counters later, as I do not have the information now (it was determined by my SQL-expert colleague)