| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Total_agents
|
The total number of agents currently registered in the database manager instance that is being monitored (Sum of coordinator agents and subagents) |
Number
|
This measure can be used to evaluate the setting for MAXAGENTS configuration parameter. |
| Agents_idle
|
The percentage of agents in the agent pool that is currently unassigned to an application and are, therefore, “idle” |
Percent
|
Having idle agents available to service requests for agents can improve performance. So you can use this measure to help set the NUM_POOLAGENTS configuration parameter. |
| Agents_waiting_on_token
|
The percentage of agents waiting for a token so they can execute a transaction in the database manager |
Percent
|
You can use this element to help evaluate your setting for the MAXCAGENTS configuration parameter. Each application has a dedicated coordinator agent to process database requests within the database manager. Each agent has to get a token before it can execute a transaction. The maximum number of agents that can execute database manager transactions is limited by the configuration parameter MAXCAGENTS. |
| Agents_creation_ratio
|
The ratio of number of agents assigned directly from agent pool to the total number of agents used to service requests |
Percent
|
A high percentage indicates the effectiveness of the agent pool. A consistent low value indicates that the number of agents in the agent pool are not adequate to service requests and hence the NUM_POOLAGENTS setting has to be increased. |
| Agents_stolen
|
The number of times that agents are stolen from an application. Agents are stolen when an idle agent associated with an application is reassigned to work on a different application
|
Number
|
If this value is high, consider increasing the NUM_POOLAGENTS configuration parameter.
|