bklockwood
commented
9 years ago Might do this later on, but for now, deferred.
Open Rabbit994 opened 9 years ago
bklockwood
commented
9 years ago Might do this later on, but for now, deferred.
CAS Servers: \MSExchange RPCClientAccess\RPC Requests - RPC Requests being processed, anything above 40 indicates bottleneck \MSExchange RPCClientAccess\RPC Averaged Latency - RPC Average Latency (CAS) - Anything above 250 indicates bottleneck
Hub: \MSExchangeTransport Queues(_total)\Aggregate Delivery Queue Length (All Queues) - Anything above 200 means your queues are backing up
Mailbox: \MSExchange Replication(_total)\ActivationSuspended \MSExchange Replication(_total)\Failed \MSExchange Replication(_total)\FailedSuspended \MSExchange Replication(_total)\Suspended Anything above 0 is bad. BADDD! (These are DAG counters indicating replication) They can be applied to standalone MBX servers not in a DAG, they will return 0 always
\MSExchangeIS Client(_Total)\RPC Average Latency - The best counter for MBX servers, anything above 50 indicates bottleneck, almost always disk, this should be averaged since spikes aren't unusual, it's when it sustained that it's issue
\MSExchange Database(Information Store)\Log Record Stalls/sec - Means Logs are sitting in memory waiting to get written (above 10 is bad) \MSExchange Database(Information Store)\Log Threads Waiting - Different counter, same thing, logs waiting time on disk, above 10 is bad
\MSExchange Database(Information Store)\I/O Database Reads Average Latency - Overall database read latency, Microsoft says anything above 20 is bad, I'm generally cool with anything up to 100 \MSExchange Database(Information Store)\I/O Database Writes Average Latency - Overall database write latency, anything past 200 is bad, writes are less priority is then reads
Last 4 counters will generally show up in Disk Average Read/Write Latency issues as well but I love knowing application health because on Application servers, that's what you care about, their health