The following counters are relevant to individual hub queues:
|
Policy engine hub objects and counters |
Description |
|---|---|
|
Allocation queue pending items |
The number of items in the queue waiting to be allocated to a policy engine. |
|
Byte limit (higher) |
The maximum size of message events that can be processed by the current queue. This value is the basis for the MaxSizeBytes hub registry value. |
|
Byte limit (lower) |
The minimum size of message events that can be processed by the current queue. If the hub only supports a single (default) queue, this lower limit is zero bytes; if multiple queues are defined, the lower limit is always zero bytes for the smallest size queue. |
|
Configured active engines |
The number of configured active policy engines available to this queue. |
|
Configured standby engines |
The number of configured standby policy engines available to this queue. |
|
Connected active engines |
The number of active policy engines with which a connection has been established and available to this queue. |
|
Connected standby engines |
The number of standby policy engines with which a connection has been established and available to this queue. |
|
Failure Mode |
A Boolean value specifying whether the queue is currently rejecting new events because there have been no connected PEs for more than a configured period of time. |
|
Items failed (timeout) |
The number of items failed by event timeout. |
|
Items received |
The number of items passed to the queue for analysis. |
|
Items received (supplemental) |
The total number of items poached from other queues by the policy engines assigned to the current queue. |
|
Processed items/sec |
The rate at which items are being passed to the queue. |
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |