| Measurement |
Description |
Measurement
Unit |
Interpretation |
| ConnCache_active_conn |
Indicates the number of active connections in all connection caches for this interface. |
Number |
|
| ConnCache_idle_conn |
Indicates the current number of idle connections in all connection caches for this interface. |
Number |
Ideally, the value of this measure should be zero, as idle connections in a cache are only resource drainers. |
| RPC_Requests_outstanding |
Indicates the current number of outstanding RPC requests for this interface. |
Number |
Ideally, the value of this measure should be 0. |
| RPC_Bytes_sent_average |
Indicates the average number of bytes, sent to the server in one RPC call via this interface. |
KB |
These measures serve as good indicators of the data load generated by the RPC traffic to and from the Hub transport server. |
| RPC_Bytes_received_avera |
Indicates the the average number of bytes, received from the server in one succeeded RPC call via this interface. |
KB |
| RPC_Latency_average |
Indicates the average latency in milliseconds, averaged across all RPC operations in the past 1024 RPC packets. |
MSecs |
Average is calculated over all RPCs since exrpc32 was loaded.
Ideally, this value should be less than 25 ms.
High RPC latencies often cause significant delays in the Mailbox server - Hub Transport server interactions, and hence need to be eliminated. |
| RPC_Slow_requests |
Indicates the percentage of slow RPC requests in the RPC queue, currently. |
Percent |
A slow RPC request is one that has taken more than 2 seconds. Any value higher than 5% for this measure is a cause for concern. |
| RPC_Requests_failed |
Indicates the percentage of requests in the RPC queue that currently failed. |
Percent |
Ideally, this value should be 0. A non-zero value for this measure might warrant an investigation. |
| RPC_Requests_succeeded |
Indicates the percentage of RPC requests in the queue that currently succeeded. |
Percent |
|