This chapter describes Oracle WebLogic Server metrics.
This category provides information about application metrics.
For the selected application, the total number of EJBs currently in the EJB cache.
For the selected application, the number of cache access attempts per minute in the last 5 minutes.
For the selected application, this metric shows the total number of EJBs that have been activated since the server started.
For the selected application, the percentage of cache accesses that completed successfully in the last 5 minutes. The value of this metric can range between zero and 100.
For the selected application, the number of cache misses per minute in the last 5 minutes.
For the selected application, the EJB pool accesses per minute in the last 5 minutes.
For the selected application, the percentage of pool accesses that were successful in the last 5 minutes.
For the selected application, the current number of available bean instances in the free pool.
For the selected application, the bean destroys performed per minute in the last 5 minutes.
For the selected application, failed EJB pool accesses per minute in the last 5 minutes.
For the selected application, the number of bean instances currently being used from the free pool.
For the selected application, the percentage of transactions that were committed during the last 5 minutes.
For the selected application, the transaction commits per minute for the last 5 minutes.
For the selected application, the total number of transactions that have been rolled back for this EJB since the server started.
For the selected application, the transaction timeouts per minute for the last 5 minutes.
For the selected application, the number of messages processed by message-driven beans (MDBs) per minute in the last 5 minutes.
For the selected application, this metric shows the average number of servlet and/or JSP invocations per minute, averaged over the past five minutes.
For the selected application, this metric shows the average amount of time (in milliseconds) spent executing servlets and/or JSPs over the last five minutes.
This metric shows the number of active sessions for the selected application.
For the selected application, the number of waiting requests in the work manager queue.
For the selected application, the number of requests processed per minute in the last 5 minutes.
For the selected application, this metric shows the number of work manager requests waiting in the queue.
This category provides information about application metrics.
This metric shows the current status of the application, indicated as an integer value:
1 - the application is considered up and running
0 - the application is considered down
On an Enterprise Manager page, the status is shown by an icon that graphically indicates whether the application is up and running or not.
This category provides information about datasource metrics.
For the selected data source, this metric shows the number of database connections currently available (not in use).
For the selected data source, this metric shows the number of database connections created per minute, averaged over the past five minutes.
For the selected data source, this metric shows the number of JDBC connections currently in use by applications.
For the selected data source, this metric shows the number of JDBC connection leaks per minute, averaged over the past five minutes.
For the current data source, this metric shows the current count of JDBC connections in the JDBC connection pool.
For the selected data source, this metric shows the number of failed JDBC connection refreshes per minute, averaged over the past five minutes.
For the selected data source, this metric shows the number of failed JDBC connection requests per minute, averaged over the past five minutes.
For the selected data source, this metric shows the number of requests for a JDBC connection from this data source per minute, averaged over the past five minutes.
For the selected data source, this metric shows the percentage of requests that successfully returned JDBC connections during the last five minutes.
For the selected data source, this metric shows the number of database connections that are currently unavailable (in use or being tested by the system).
For the selected data source, this metric shows the current number of JDBC connection requests waiting for a database connection.
For the selected data source, this metric shows the number of JDBC connection wait failures per minute, averaged over the past five minutes.
A wait failure is a request for a connection from this data source that had to wait before getting a connection and eventually failed to get a connection. Waiting connection requests can fail for a variety of reasons, including waiting for longer than the ConnectionReserveTimeoutSecond.
For the selected data source, this metric shows the number of JDBC connection waits per minute, averaged over the past five minutes.
A JDBC connection wait is a request for a connection from this data source that had to wait before getting a connection, including those that eventually got a connection and those that did not get a connection
For the selected data source, this metric shows the percentage of requests waiting for a JDBC connection that successfully got a connection during the last 5 minutes.
A JDBC connection wait is a request for a connection from this data source that had to wait before getting a connection, including those that eventually got a connection and those that did not get a connection
For the selected data source, this metric shows the number of JDBC connection wait successes per minute, averaged over the past five minutes.
A wait success is a request for a connection from this data source that had to wait before getting a connection and eventually succeeded in getting a connection.
For the selected data source, this metric shows 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
For the selected data source, this metric shows the number of statements per minute added to the statement cache, averaged over the past five minutes.
For the current data source, this metric shows the number of statements per minute discarded from the statement cache, averaged over the past five minutes.
For the selected data source, this metric shows the number of statements per minute not satisfied by the statement cache, averaged over the past five minutes.
For the selected data source, this metric shows the percentage of statements satisfied by the statement cache during the last 5 minutes.
For the selected data source, this metric shows the number of statements per minute satisfied by the statement cache, averaged over the past five minutes.
For the current data source, this metric shows the number of prepared and callable JDBC statements currently cached in the connection pool.
Each JDBC 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.
For the current EJB module, this metric shows the number times per minute that an attempt was made to access the EJB cache. This value is averaged over the last 5 minutes.
For the current EJB module, this metric shows the total number of beans per minute that have been activated in the last 5 minutes.
For the current EJB module, this metric shows the percentage of cache accesses that completed successfully in the last 5 minutes.
For the current EJB module, this metric shows the number of cache misses per minute in the last 5 minutes.
For the current EJB module, this metric shows the total number of beans per minute that have been passivated in the last 5 minutes.
For the current EJB module, this metric shows how many times the EJB pool has been accessed per minute. This is averaged over the last 5 minutes.
For the current EJB module, this metric shows the percentage of pool accesses that were successful in the last 5 minutes.
For the selected EJB, this metric shows the current number of available bean instances in the free pool.
For the selected EJB Module, this metric shows the bean destroys per minute in the last 5 minutes.
For the selected EJB module, this metric shows the failed pool accesses per minute over the past five minutes.
For the current EJB module, this metric shows the number of bean instances currently being used from the free pool.
For the selected EJB module, this metric shows the transaction commits per minute, averaged over the past five minutes.
For the selected EJB module, this metric shows the number of transaction rollbacks per minute over the past five minutes
This category provides information about EJB pool metrics.
This metric shows how many times per minute that the selected EJB pool has been accessed over the last 5 minutes.
This metric shows the percentage of attempts to access the pool that were successful in the last 5 minutes.
This metric shows the current number of available bean instances in the selected EJB pool.
For the selected EJB pool, this metric shows the bean destroys per minute over the last 5 minutes.
This category provides information about EJB transaction metrics.
This metric shows the percentage of EJB transactions that were committed during the last five minutes.
This metric shows the EJB transaction commits per minute, averaged over the past five minutes.
This category provides information about JMS metrics.
This category provides information about JMS server metrics.
For the current JMS server, this metric shows the number of bytes in all the messages that are currently available to be paged out, but which have not yet been paged out.
The JMS server attempts to keep this number smaller than the "MessageBufferSize" parameter.
For the selected JMS server, this metric shows the number of bytes per minute that were read from the paging directory, averaged over the past five minutes.
For the current JMS server, this metric shows the number of bytes per minute that were written to the paging directory, averaged over the past five minutes.
This metric shows the current number of bytes pending (unacknowledged or uncommitted) stored on the selected JMS server. Pending bytes are over and above the current number of bytes.
This metric shows the number of bytes received by the selected JMS server in the past five minutes.
This metric shows the current number of destinations defined for the selected JMS server.
This metric shows the current number of messages stored on this JMS server. This number does not include the pending messages.
This metric shows the number of messages per minute that were written to the paging directory, averaged over the past five minutes.
This metric shows the current number of pending messages (unacknowledged or uncommitted) stored on this JMS server. Pending messages are over and above the current number of messages.
This metric shows the number of messages received by this JMS server in the past five minutes.
This category provides information about JTA metrics.
For the selected server, this metric shows the number of transactions abandoned per minute, averaged over the past five minutes.
For the selected server, this metric shows the percentage of transactions committed over the last five minutes.
For the selected server, this metric shows the total number of transactions committed per minute, averaged over the past five minutes.
For the selected server, this metric shows the total number of seconds that JTA transactions were active for all committed transactions.
For the selected server, this metric shows the number of transactions that completed with a heuristic status per minute, averaged over the past five minutes.
For the selected server, this metric shows the number of transactions processed per minute, averaged over the past five minutes.
For the selected server, this metric shows the number of transactions rolled back per minute, averaged over the past five minutes.
For the selected server, this metric shows the number of transactions rolled back due to an application error per minute, averaged over the past five minutes.
For the selected server, this metric shows the number of transactions rolled back due to a resource error per minute, averaged over the past five minutes.
For the selected server, this metric shows the number of transactions rolled back due to an internal system error per minute, averaged over the past five minutes.
This category provides information about JVM metrics.
This metric shows the number of Java classes currently loaded into the selected Java Virtual Machine (JVM).
his category provides information about JVM compilation metrics.
For the selected Java Virtual Machine (JVM), this metric shows the total time spent by the JVM in compilation. The value of the metric is in milliseconds and shows the time spent in compilation since the JVM was last started.
This metric shows the percentage of the CPU currently in use by the Java Virtual Machine (JVM). This includes the load that the JVM is placing on all processors in the host computer.
For example, if the host uses multiple processors, the value represents a snapshot of the average load on all the processors.
This metric shows the number of daemon Java threads currently running in the Java Virtual Machine (JVM) across all processors.
This metric shows the current size of the Java Virtual Machine (JVM) memory heap, in megabytes.
This metric shows the name vendor responsible for the current Java Development Kit (JDK) that is being used for the current Java Virtual Machine.
For example, when you install and configure an Oracle WebLogic Server domain, you can choose to use the standard Sun Microsystems JDK or the Oracle WebLogic Server JRockit JDK.
This category provides information about JVM garbage collectors metrics.
This category provides information about JVM memory pools metrics.
This category provides information about JVM memory usage metrics.
This metric shows the total heap memory (in kilobytes) currently in use by the selected Java Virtual Machine (JVM).
This metric shows the amount of memory that is currently allocated to the nursery, in megabytes.
The nursery is the area of the Java heap that the virtual machine allocates to most objects. Instead of garbage collecting the entire heap, generational garbage collectors focus on the nursery.
Most objects do not last a long time in memory; as a result, in most cases, it is sufficient to perform garbage collect on only the nursery and not on the entire memory heap.
If you are not using a generational garbage collector, the nursery size is zero.
This metric shows how long the selected Java Virtual Machine (JVM) has been up in running (in milliseconds).
This category provides information about JVM thread contention metrics.
This metric shows the number of times the selected Java Virtual Machine (JVM) thread has been blocked since the thread was started.
This metric shows how long (in seconds) this thread has been blocked since it was started or since thread contention monitoring was enabled.
This metric shows the amount of CPU (in seconds) that is currently being used by the selected Java Virtual Machine (JVM) thread.
This metric shows the name of the lock the selected Java Virtual Machine (JVM) thread is blocked on (if applicable).
This metric shows the state of the selected Java Virtual Machine (JVM) thread.
The state can be any of the states defined here on the Sun Java Web site.
This metric shows the number of Java threads (daemon and non-daemon) that are currently running in the virtual machine across all processors.
This category provides information about JVM threads metrics.
This metric shows the current number of active daemon threads in the selected Java Virtual Machine (JVM).
This metric shows the current number of deadlocked threads in the selected Java Virtual Machine (JVM).
This metric shows the maximum (peak) number of threads started in this Java Virtual Machine (JVM) since the JVM was started.
This category provides information about response metrics.
This metric shows the status of the selected server. The value is an integer, where "1" means that the server is up and running and "0" means the server is down and unavailable.
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 Server instance is down |
This category provides information about server metrics.
This metric returns the port number on which the WebLogic server is listening for requests.
This metric shows the current number of sockets listening on this server.
This value is equal to the number of sockets registered with the tuning muxer. For more information, see "Tuning Muxers" in Oracle Fusion Middleware Performance and Tuning for Oracle WebLogic Server.
This category provides information about server datasource metrics.
The number of database connections currently available (not in use) in this data source.
For the selected server, the number of database connections created per minute in the last 5 minutes.
For the selected server, the number of JDBC connections currently in use by applications on the server.
For the current server, the current count of JDBC connections in the connection pool in the data source.
The number of connection requests per minute for a connection from this data source in the last 5 minutes.
The percentage of connection requests that successfully returned connections during the last 5 minutes.
The current number of connection requests waiting for a database connection.
The number of connection waits per minute in the last 5 minutes.
The percentage of requests waiting for a connection that successfully got a connection during the last 5 minutes.
The number of connection wait successes per minute in the last 5 minutes.
The number of statements per minute added to the statement cache in the last 5 minutes.
The number of statements per minute not satisfied by the statement cache in the last 5 minutes.
The percentage of statements satisfied by the statement cache during the last 5 minutes.
The number of statements per minute satisfied by the statement cache in the last 5 minutes.
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 server overview metrics.
For the selected server, the number of database connections created per minute in the last 5 minutes.
The number of EJB cache access attempts per minute in the last 5 minutes on the selected server.
The total number of Java beans per minute that have been activated in the last 5 minutes.
The percentage of EJB cache accesses that completed successfully in the last 5 minutes.
For the selected server, this metric displays the percentage of EJB pool accesses that were successful in the last 5 minutes.
For the selected server, this metric indicates the current number of available Java bean instances in the free pool.
For the selected server, this metric shows the bean destroys per minute in the last 5 minutes.
For the selected server, this metric shows the percentage of pool accesses that were successful in the last 5 minutes.
For the selected server, this metric shows the percentage of EJB transactions that were committed during the last 5 minutes.
For the selected server, this metric identifies the EJB transaction commits per minute for the last 5 minutes.
For the selected server, this metric specifies the percentage of transactions that were committed during the last 5 minutes.
This metric shows the EJB transaction timeouts per minute for the last 5 minutes on the selected server.
The total number of JTA transactions committed per minute on this server in the last 5 minutes.
The number of JTA transactions rolled back per minute in the last 5 minutes on the selected server.
For the selected server, this metric specifies the number of messages processed by message-driven beans (MDBs) per minute in the last 5 minutes.
The current number of messages pending (unacknowledged or uncommitted) stored on the JMS servers deployed on this WebLogic Server instance. Pending messages are over and above the current number of messages.
The current number of JMS messages stored on the JMS servers deployed on this WebLogic Server instance. This number does not include the pending messages.
For the selected server, the average number of servlet and/or JSP invocations per minute in the last 5 minutes.
For the selected server, the average amount of time spent executing servlets and/or JSPs in the last 5 minutes (milliseconds)
This category provides information about server work manager metrics.
For the selected server, this metric shows the number of work manager requests pending in the queue.
This category provides information about server/JSP metrics.
This metric shows the average number of reloads per minute of the selected servlet or JSP in the last 5 minutes.
This category provides information about servlet rollup metrics.
This metric provides details about the servlet invocations that are active and are currently in the web container. Active invocation refers to the number of requests that are currently being processed by the server.
This metric indicates the time taken to execute the servlet during the last interval.
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 15 Minutes | After Every Sample | > | Not Defined | Not Defined | 1 | The Current Client Processing time for servlet %Name% is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name", "Application Name", and "Web Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "Name", "Application Name", and "Web Application Name" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name", "Application Name", and "Web Application Name" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric indicates the average time taken by a servlet to respond.
This metric indicates the number of number of requests to the server per second.
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 15 Minutes | After Every Sample | > | Not Defined | Not Defined | 1 | The invocations per second for Servlet %Name% is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name", "Application Name", and "Web Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "Name", "Application Name", and "Web Application Name" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name", "Application Name", and "Web Application Name" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This category provides information about Web module metrics.
For the selected Web module, this metric shows the average number of invocations per minute of servlets and/or JSPs in the last 5 minutes.
This category provides information about Java JEE service endpoints metrics.
This metric shows the total amount of dispatch time since the Web service was started.
This metrics represents the total time that the Web service port has spent executing since the Web service was started.
This metric represents the total number of invocations for the selected Web services port since the Web service was started.
This category provides information about work manager metrics.
This metric shows the number of work manager requests processed per minute, averaged over the past five minutes.