You can use customized charting to determine if you are meeting your business and performance goals. You can track statistics such as availability, response time, traffic, and throughput on various components of your environment, such as your service policies, applications, servers, dynamic clusters, and nodes.
To view this administrative console page, click
.Specifies global preferences for all your chart groups.
To create a new chart within the chart group, click Open a new chart tab. To open the currently selected chart into a new window, click View chart in new window. To return the chart from the new window to the chart group, click View chart in chart group.
Click Preferences for the individual chart to update the chart preferences. These changes apply only to the currently selected chart.
Use these buttons to change the data that displays in the chart and table.
This metric measures the number of concurrent requests per the defined data set selection within the data name selection.
The average throughput metric is calculated in seconds based on the total workflow requests to the on demand router, as defined by the data scope, data name and data set.
The average response time metric is the time in milliseconds it takes for a work request to complete. This metric includes the request from inception, until the request is returned to the client, and is the equivalent of the service time metric plus the wait time in queue metric.
This metric is the average time in milliseconds that a work request spends waiting to service.
The time in milliseconds to service a request for the on demand router. This metric indicates the time that the on demand router spends getting work to the node where it is completed.
The average number of requests queued per second for any work queue in the environment that is defined by the data scope, data set, and data name.
The average drop rate is calculated based on the number of work requests that are not processed due to a full queue. Work requests that encounter a full queue are returned to the requestor with an error.
The relative performance of the configured goal compared to the actual goal value.
The percentage of requests of the service policy percentile goal that meet the specified response time.
The number of seats required for a given dynamic cluster's load coming through a given gateway.
Memory used by a process.
CPU utilization by a process.
Total requests for Web modules deployed to a process.
Total time in seconds that the process has been running.
Total method calls for EJB modules deployed to a process.
Total transactions for a partition.
Free memory on a node.
The percentage of the resources that are being used and how much resource is available. Utilization measures the node speed and process CPU.
The number of jobs that arrive at the execution environment (endpoint application) for processing.
The number of jobs which run to completion at the execution environment.
The total time in milliseconds that jobs spend executing.
The maximum concurrency level that is attained.
The number of jobs that are queued at the scheduler.
The number of jobs that are dispatched by the scheduler.
The number of jobs that failed in the execution environment.
The number of dispatch errors that occurred for jobs.
The time in milliseconds jobs spent in the queue.
The total time in milliseconds jobs spent being dispatched.
The time in milliseconds for jobs spent being dispatched when dispatch errors occurred.
A floating-point number of MHz of the reference instruction set specified for each node.
CPU consumption by WebSphere® processes on a node.
CPU consumption by other processes on a node.
Available processor capacity of a node. This is the total CPU capacity minus the consumption by WebSphere and non-WebSphere processes
Total memory of a process or node.
A work factor characterizes the average amount of computational work required to serve a request of a given kind
The required processing power for a given deployment target.
The expected memory consumption of a server instance to be started.
Resident memory of a process.
The average amount of computing power consumed on a given processing tier by one active request of a given flow, averaged from (a) the time when the autonomic request flow manager (ARFM) gateway forwarded the request to the target server and (b) the time the reply came back from the target server.
Specifies the percentage of entitled capacity that is being used by a server partition. This metric is only available for AIX® shared-uncapped micro-partitions.
Specifies the maximum percentage of entitled capacity that a server partition can use. This metric is only available for AIX shared-uncapped micro-partitions. The value of this metric is calculated from the idle cycles that are in the shared processor pool for the particular server partition.
(%entitled capacity / %max enttiled capacity) * 100
This
metric is only valid for AIX shared-uncapped
micro-partitions.Specifies the number of physical processors that are being used by the shared server partition. This metric is only valid for AIX shared-uncapped micro-partitions.
Specifies the number of processors available in the shared processor pool to which this server partition belongs. This metric is only valid for AIX shared-uncapped micro-partitions.
Specifies the rate of admission for requests without server affinity, plus the number of session-initiating requests.
Specifies the rate of refusal for requests without server affinity, plus the number of session-initiating requests that were refused.
Choose the object instance and click OK, unless you select the Component stability scope. The default scope is Component stability, and no filtering occurs on the list of available data set objects to chart.
The chart table displays a list of the data that is included in the chart.
To save the chart group, enter a name and click Save.
To remove the current chart group, click Remove chart group.