Monitoring Run-time States for webMethods Broker
In response to the sagcc get monitoring runtimestate and sagcc get monitoring state commands, webMethods Broker provides information about the following key performance indicators (KPIs):
KPI | Description |
Data storage or configuration storage usage | Use this KPI to monitor the Broker Server run-time memory storage or configuration storage so that you can take corrective actions if storage use approaches a critical value. The marginal, critical, and maximum values for this KPI depend on the maximum storage size configured for Broker Server.  Marginal is 60% of the maximum storage size.  Critical is 80% of the maximum storage size.  Maximum is the configured storage size. |
Memory usage | Use this KPI to monitor use of Broker Server main memory so that you can take corrective actions if memory use approaches a critical value. The marginal, critical, and maximum values for this KPI depend the amount of main memory configured in the Broker Server configuration file (awbroker.cfg).  Marginal is 80% of the maximum main memory.  Critical is 95% of the maximum main memory.  Maximum is the configured amount of main memory. |
Stalled queues | Use this KPI to monitor stalled queues. A queue is considered stalled only if all the following conditions are true for that queue:  A client is connected to the queue.  The queue contains at least one message.  More than five minutes has elapsed since the last time the client retrieved a message from the queue. The KPI uses the following marginal, critical, and maximum values:  Marginal is 1 stalled queue.  Critical is 50% of the maximum number of queues.  Maximum is determined by the greatest value among the following conditions:  1 queue  5% of the total number of client or forward queues in all Brokers.  Current number of stalled queues. |