Here the most important performance counters and their thresholds is critical to establishing a performance baseline and monitoring plan to proactively monitor your Exchange 2010 environment and troubleshoot and resolve issues when they arise
back to Performance and Threshold Counters for Exchange Server 2010 - All in One
Transport Disk Counters
Logical/Physical Disk(*)\Avg. Disk sec/Read | Should be less than 20 milliseconds (ms) on average. |
Shows the average time, in seconds, of a read of data from the disk. | Spikes (maximum values) should not be higher than 50 ms. |
Logical/Physical Disk(*)\Avg. Disk sec/Write | Should be less than 20 ms on average. |
Shows the average time, in seconds, of a write of data to the disk. | Spikes (maximum values) should not be higher than 50 ms. |
Transport Queue Length Counters
\MSExchangeTransport Queues(_total)\Aggregate Delivery Queue Length (All Queues) | Should be less than 3,000 and not more than 5,000. |
Shows the number of messages queued for delivery in all queues. | |
\MSExchangeTransport Queues(_total)\Active Remote Delivery Queue Length | Should be less than 250 at all times. |
Shows the number of messages in the active remote delivery queues. | |
\MSExchangeTransport Queues(_total)\Active Mailbox Delivery Queue Length | Should be less than 250 at all times. |
Shows the number of messages in the active mailbox queues. | |
\MSExchangeTransport Queues(_total)\Submission Queue Length | Should not exceed 100. |
Shows the number of messages in the submission queue. | If sustained high values are occurring, investigate Active Directory and Mailbox servers for bottlenecks or performance-related issues. |
\MSExchangeTransport Queues(_total)\Active Non-Smtp Delivery Queue Length | Should be less than 250 at all times. |
Shows the number of messages in the Drop directory that is used by a Foreign connector. | |
\MSExchangeTransport Queues(_total)\Retry Mailbox Delivery Queue Length | Should be less than 100 at all times. |
Shows the number of messages in a retry state attempting to deliver a message to a remote mailbox. | |
\MSExchangeTransport Queues(_total)\Retry Non-Smtp Delivery Queue Length | Should not exceed 100. |
Shows the number of messages in a retry state in the non-Simple Mail Transfer Protocol (SMTP) gateway delivery queues. | |
\MSExchangeTransport Queues(_total)\Retry Remote Delivery Queue Length | Should not exceed 100. |
Shows the number of messages in a retry state in the remote delivery queues. | We recommend that you check the next hop to determine the causes for queuing. |
\MSExchangeTransport Queues(_total)\Unreachable Queue Length | Should not exceed 100. |
Shows the number of messages in the Unreachable queue. | |
\MSExchangeTransport Queues(_total)\Largest Delivery Queue Length | Should be less than 200 for the Edge Transport and Hub Transport server roles. |
Shows the number of messages in the largest delivery queues. | |
\MSExchangeTransport Queues(_total)\Poison Queue Length | Should be 0 at all times. |
Shows the number of messages in the poison message queue. |
Transport Database Counters
MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Log Writes/sec | Not Applicable |
Shows the rate of log file write operations completed. | |
Determines the current load. Compare values to historical baselines. | |
MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Log Reads/sec | Not Applicable |
Shows the rate of log file read operations completed. | |
Determines the current load. Compare values to historical baselines. | |
MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\Log Generation Checkpoint Depth | Should be less than 1,000 at all times. |
Represents the amount of work, in count of log files, that need to be redone or undone to the database files if the process fails. | |
MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\Version buckets allocated | Should be less than 200 at all times. |
Total number of version buckets allocated | |
Shows the default backpressure values as listed in the edgetransport.exe.config file. | |
Exchange 2007 release to manufacturing (RTM) version – Medium=60, High =100 | |
Exchange 2007 SP1 version – Medium=120, High=200 | |
For more database cache size guidance, see New maximum database cache size guidance for Exchange 2007 Hub Transport server role. | |
MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Database Reads/sec | Not Applicable |
Shows the rate of database read operations completed. | |
Determines the current load. Compare values to historical baselines. | |
MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Database Writes/sec | Not Applicable |
Shows the rate of database write operations completed. | |
Determines the current load. Compare values to historical baselines. | |
MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\Log Record Stalls/sec | Should be less than 10 per second on average. |
Shows the number of log records that cannot be added to the log buffers per second because they are full. If this counter is non-zero most of the time, the log buffer size may be a bottleneck. | Spikes (maximum values) should not be greater than 100 per second. |
MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\Log Threads Waiting | Should be less than 10 threads waiting on average. |
Shows the number of threads waiting for their data to be written to the log to complete an update of the database. If this number is too high, the log may be a bottleneck. |
Extensibility Agent Counters
MSExchange Extensibility Agents(*)\Average Agent Processing Time (sec) | Should be less than 20 at all times. |
Shows the average agent processing time in seconds per event. | Sustained higher latencies may indicate a hung agent. |
MSExchange Extensibility Agents(*)\Total Agent Invocations | Not Applicable |
Shows the total number of invocations since the last restart. | |
Shows the current invocation rate. |
-Dario
Counters | Threshold |
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.