This chapter describes metrics for Java EE applications deployed to Oracle WebLogic Server.
Metrics concerning ADFc (ADF Controller)
The count of active task flows in an ADF application since the application was run. This metric records the number of times that a task flow has been the active task flow for a user.
For example, if the user goes from task flow A to task flow B and then exits back to A, then task flow A will have been active two times and task flow B active once. Therefore the total active count would be three.
This metric represents the number of currently active ADF task flows.
The rate at which task flows are processed since the data was last collected.
The number of active task flows processed since the last time metric data was collected.
This metric displays the number of task flows entered at the current time.
This metric records the number of times a task flow has been entered. Exiting back into a task flow from a called task flow is not the same as entering it. For example, if the user goes from task flow A to task flow B and then exits back to A, the total would be two, one entry for each into A and B.
This metric records the number of times the task flow has been called by a task flow call activity.
Not every task flow is initiated by a task flow call activity. In most cases, this is probably going to be the same as number of entered task flows, but not all the time.
The number of invoked task flows that have been completed at the current time.
The average time taken over the past five minutes to invoke ADF taskflows.
The average time to process task flows since the data was last collected.
The average creation time for an ApplicationModule instance since the data was last collected.
The maximum creation time for an Application Module instance since the data was last collected.
For the selected ApplicationModule, the count of available ApplicationModule instances in the pool over the past five minutes.
For the selected ApplicationModule, the count of available ApplicationModule instances in the pool over the past one minute.
For the selected ApplicationModule, the number of unavailable ApplicationModule instances in the pool over the past five minutes.
For the selected ApplicationModule, the count of unavailable ApplicationModule instances in the pool over the past one minute.
The name of the ApplicationModule to which the following metrics apply.
The number of ApplicationModule instances checked into the ApplicationModule pool since the data was last collected.
The number of ApplicationModule instances checked out of the ApplicationModule pool since the data was last collected.
This category provides information about datasource metrics.
This metric shows the number of database connections currently available (not in use) for this data source.
This metric shows the average number of database connections created for this data source per minute in the last 5 minutes.
This metric shows the number of data source connections that are currently in use by applications.
For the selected data source, this metric shows the average number of JDBC connection leaks per minute over the last 5 minutes. A leaked connection is a connection that was reserved from the data source but was not returned to the data source when the connect was closed.
This metric shows the current number of JDBC connections in the connection pool in the selected data source.
This metric shows the average number of times per minute that the data source attempted to refresh a database connection and failed over the past five minutes.
This metric shows the average number of failed connection requests per minute in the last 5 minutes.
This metric shows the average number of requests for a connection from this data source per minute over the last 5 minutes.
This metric shows the percentage of requests that successfully returned connections for this data source over the last 5 minutes.
This metric shows the number of database connections that are currently unavailable (in use or being tested by the system) in this instance of the data source.
This metric shows the current number of connection wait requests for this data source.
A connection wait request is a request that had to wait for a database connection.
For the current data source, this metric shows the average number of connection wait requests that failed per minute over the past five minutes.
A connection wait request is a request for a database connection that had to wait before getting a connection.
Connection wait requests can fail for a variety of reasons, including waiting for longer than the value of the ConnectionReserveTimeoutSeconds property.
For the selected data source, this metric shows the average number of connection wait requests per minute in the last 5 minutes.
A connection wait request is a request for a connection that had to wait before getting a connection. This metric includes those that eventually got a connection and those that did not get a connection.
For the current data source, this metric shows the percentage of connection wait requests that successfully got a database connection during the last 5 minutes.
A connection wait request is a request for a connection that had to wait before getting a connection. This metric includes those that eventually got a connection and those that did not get a connection.
For this data source, this metric shows the average number of connection wait requests that succeeded per minute over the last 5 minutes.
A connection wait request succeeds when it eventually gets a database connection.
The current state of the data source. Possible states are:
Running - the data source is enabled (deployed and not suspended). This is the normal state of the data source.
Suspended - the data source has been manually disabled.
Shutdown - the data source is shutdown and all database connections have been closed.
Overloaded - all resources in pool are in use.
Unhealthy - all connections are unavailable (not because they are in use). This state occurs if the database server is unavailable when the data source is created (creation retry must be enabled) or if all connections have failed connection tests (on creation, on reserve, or periodic testing).
Unknown - the data source state is unknown
This metric shows the number of statements per minute that were added to the statement cache for this data source in the last 5 minutes.
This metric shows the average number of statements per minute that were discarded from the cache over the past five minutes.
Each connection in the connection pool has its own cache of statements. This number is the sum of the number of statements that were discarded from the caches for all connections in the connection pool.
This metric shows the average number of statements per minute not satisfied by the statement cache in the last 5 minutes.
Each connection in the connection pool has its own cache of statements.
This metric shows the percentage of statements satisfied by the statement cache during the last 5 minutes.
Each connection in the connection pool has its own cache of statements.
This metric shows the average number of statements per minute satisfied by the data source statement cache in the last 5 minutes.
Each connection in the connection pool has its own cache of statements.
This metric shows the number of prepared and callable statements currently cached in the statement.
Each connection in the connection pool has its own cache of statements. This number is the sum of the number of statements in the caches for all connections in the connection pool.
This category provides information about EJB module metrics.
This metric shows the total number of beans from this EJB Home that are currently in the EJB cache.
This metric shows the average number of beans per minute that have been activated from the EJB home over the last 5 minutes.
This metric shows the percentage of cache accesses that completed successfully in the last 5 minutes.
This metric shows the average number of cache misses per minute for this EJB module in the last 5 minutes.
This metric shows the average EJB pool accesses per minute over the last 5 minutes.
This metric shows the percentage of EJB pool accesses that were successful in the last 5 minutes.
This metric shows the current number of available EJB instances in the free pool.
This metric shows the average number of EJB destroys per minute for this EJB module over the last 5 minutes.
This metric shows the average number of times per minute that a failed attempt was made to get an instance from the free pool. This value is averaged over the past five minutes.
An Attempt to get a bean from the pool will fail if there are no available instances in the pool.
This metric shows the number of EJB instances currently being used from the free pool.
This metric shows the average number of EJB transaction commits per minute for this EJB Module over the last 5 minutes.
This metric shows the average number of EJB transaction rollbacks per minute for this EJB module over the last 5 minutes.
This category provides information about EJB transaction metrics.
This metric shows the percentage of EJB transactions that were committed for the select EJB over the last 5 minutes.
This metric shows the average number of EJB transaction commits per minute for this EJB over the last 5 minutes.
This category provides information about the EJB overview metrics.
This metric shows the average number of EJB cache access attempts per minute for this application in the last 5 minutes.
This metric shows the average number of Enterprise Java Beans that have been activated per minute over the last 5 minutes.
This metrics indicates the percentage of cache accesses that completed successfully in the last 5 minutes.
This metric shows the average number of EJB cache misses per minute in this application in the last 5 minutes.
This metrics shows the average number of Pool accesses per minute for this application in the last 5 minutes.
This metric shows the percentage of EJB pool accesses that were successful for this application in the last 5 minutes.
This metric shows the current number of available EJB instances in the free pool.
This metric shows the average number of EJB destroys per minute for this application in the last 5 minutes.
This metric shows the average number of failed pool accesses per minute for this application in the last 5 minutes.
This metric shows the percentage of EJB transactions that were committed for this application during the last 5 minutes.
This metric shows the average number of EJB transaction commits per minute for this application in the last 5 minutes.
This metric shows the average number of EJB transaction rollbacks per minute for this application over the last 5 minutes.
This metric shows the average number of EJB transaction timeouts per minute for this application over the past 5 minutes.
This metric shows the average number of messages processed by Message Driven Beans (MDBs) per minute for this application in the last 5 minutes.
This metrics shows the average number of servlet and/or JSP invocations per minute in this application in the last 5 minutes.
This metric displays the average amount of time (in milliseconds) spent executing servlets and/or JSPs in this application in the last 5 minutes.
This metric shows the number of Work Manager requests waiting in the queue.
This category provides information about servlet/JSP metrics.
This metric shows the average number of reloads of the selected servlet or JSP per minute over the last 5 minutes.
This metric shows the average number of invocations of the selected servlet or JSP per minute over the last 5 minutes.
This category provides information about status metrics.
This metric shows the current state of the application.
This metric specifies whether this application version is the currently active version. An application can be the only version currently deployed, or it can have more than one version currently deployed, using the side-by-side deployment feature.
If more than one version is deployed, only one version can be active.
Values for this metric can be:
INACTIVE - it has not been activated yet, or that there is more than one version of the application deployed (using side-by-side deployment) and this one is retiring.
ACTIVE_ADMIN - the currently active version for administrative channel requests.
ACTIVE state the currently active version for normal (non-administrative) channel requests.
This category provides information about Web module metrics.
This metric shows the average number of servlet and JSP invocations per minute for this Web module in the last 5 minutes.
Metrics concerning MDS (Metadata Services)
The number of metadata object gets per second.
The average elapsed time in seconds to get a metadata object.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every 3 Samples | > | Not Defined | Not Defined | 2 | The average processing time of each Metadata Object Get is %value% seconds. |
This value should be considerably less than 1 second. If the value is greater than about 0.01, check the cache efficiency metrics (IOs Per Metadata Object Get and IOs Per MO Content Get), and increase the MDS cache size if those metrics indicate a problem. If those metrics are normal, the CPU may be overloaded, meaning the application may need more hardware resources, especially if performance is perceived to be slow.
The average number of physical IOs per persistence-level document get. This is an indication of the efficiency of the document cache portion of the metadata cache for the application. Ideally it should be much less than 1.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every 3 Samples | > | Not Defined | Not Defined | 2 | The average number of physical IOs per Document Get is %value%. |
The average number of physical IOs per metadata object XML content retrieval. This is an indication of the efficiency of the metadata cache for the application. Ideally it should be much less than 1.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every 3 Samples | > | Not Defined | Not Defined | 2 | The average number of physical IOs per MO Content Get is %value%. |
The average number of physical IOs per metadata object get. This is an indication of the efficiency of the metadata cache for the application. Ideally it should be much less than one.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every 3 Samples | > | Not Defined | Not Defined | 2 | The average number of physical IOs per Metadata Object Get is %value%. |
The average number of metadata objects updated per second.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
If the value of this metric is significant compared to the number of HTTP requests serviced per second, it means many users are creating or updating customizations or personalizations using the page composer or, more likely, via inherent changes. In this case, if application performance is perceived be slow, it might be wise to reduce the number of these updates by configuring the application to use a different ADF change manager (so the changes are saved in memory only, not to disk).
The average elapsed time in seconds taken to update a metadata object.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every 3 Samples | > | Not Defined | Not Defined | 2 | The average processing time of each Metadata Update is %value% seconds. |
The up or down status of the application. A value of one (1) indicates that the application is up and running; a value of zero (0) indicates that the application is down.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every Minute | After Every 60 Samples | = | Not Defined | 0 | 1 | The J2EE Application is down |