\n \n \n| Related Documentation | \nVersion of up.time \naffected | \nAffected Platforms | \n
\n \n| \n | \nAll | \nAll | \n
\n \n
...
In addition to the WebSphere metrics that up.time collects, detailed system level performance metrics are also available. This enables you to analyze system compute performance, memory usage, disk and network performance, and then relate underlying system behavior to specific metrics within WebSphere.
...
up.time collects metrics from WebSphere objects called modules. A module represents a resource category for which data is collected by the WebSphere Performance Management Infrastructure. Each module has at least one XML configuration file that lists a unique identifier for each piece of performance data contained in the module.
...
Per EJB
...
The following metrics are collected per Enterprise JavaBean (EJB) on a WebSphere server:
...
\n \n\t \n\t \n\t \n \n \n\t \n\t | The number of times that the Enterprise JavaBeans that are running on the server were created. |
\n\t \n \n \n\t \n\t | The number of times that the EJBs were removed. |
\n\t \n \n \n\t \n\t | The number of times that EJBs were removed from the cache. Note that passivation preserves the state of the EJBs on the disk. |
\n\t \n \n \n \n\t \n\t| The total number of method calls that were made to the EJBs. |
\n\t \n \n \n \n\t \n\t| The average response time, in milliseconds, on the bean methods. |
\n\t \n \n ...
Per Connection Pool
...
The following metrics are collected per connection pool on a WebSphere server:
...
\n\t | The size of the connection pool to the data source. |
\n\t| connectionPoolModule.poolSize |
\n \n \n \n\t \n\t| The number of free connections in the pool. |
\n\t | connectionPoolModule.freePoolSize |
\n \n \n \n\t \n\t | The percentage of the connection pool that is currently in use. |
\n\t | connectionPoolModule.percentUsed |
\n \n \n \n\t \n\t | The average time, in milliseconds, that a connection is used. The average time is the difference between the time at which the connection is allocated and the time at which it is returned. |
\n\t | connectionPoolModule.avgWaitTime |
\n \n \n \n\t \n\t| The total number of connections that were closed. |
\n\t | connectionPoolModule.numDestroys |
\n \n \n \n\t \n\t | The total number of connections that were created. |
\n\t| connectionPoolModule.numDestroys |
\n \n \n \n\t \n\t | The number of threads that are currently waiting for a connection. |
\n\t \n | \n \n \n\tUseTime | \n\t | The average time, in milliseconds, that a connection is used. The average use time is the difference between the time at which the connection is allocated and that time at which it is returned. |
\n\t \n \n ...
Other
...
The following metrics are collected from the WebSphere system, the Java Virtual Machine, the thread pool, or servlets:
...
\n\t| The percent of CPU resources that were used since the last query. |
\n\t | systemModule.avgCpuUtilization |
\n \n \n \n\t \n\t | The total amount of memory that is available for the Java Virtual Machine (JVM). |
\n\t | jvmRuntimeModule.totalMemory |
\n \n \n \n\t \n\t| The amount of memory that is being used by the JVM. |
\n\t| jvmRuntimeModule.usedMemory |
\n \n \n \n\t \n\t | The number of threads which are concurrently active. |
\n\t | threadPoolModule.activeThreads |
\n \n \n \n\t \n\t | The total number of global transactions that have been committed. |
\n\t | transactionModule.globalTransCommitted |
\n \n \n \n\t \n\t | The total number of global transactions that have been rolled back. |
\n\t| transactionModule.globalTransRolledBack |
\n \n \n \n\t \n\t | The number of servlet sessions that are currently cached in memory. |
\n\t | servletSessionsModule.liveSessions |
\n \n \n \n\t \n\t | The difference, in milliseconds, between the previous and current access time stamps of a servlet session. This counter does not include session time out values. |
\n\t | servletSessionsModule.timeSinceLastActivated |
\n \n \n \n\t \n\t | The average number of threads in the servlet connection thread pool. |
\n\t \n \n \n
