Oracle® Enterprise Manager Framework, Host, and Third-Party Metric Reference Manual 10g Release 2 (10.2) Part Number B16230-01 |
|
|
View PDF |
Oracle Enterprise Manager can be used to manage BEA WebLogic Managed Servers. You can use the All Metrics page for an BEA WebLogic target to view the metrics that have been collected for that target by the Oracle Management Agent.
This category of metrics provides information about the active applications. The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.Table 2-1 Active Applications Metrics
Metric | Description |
---|---|
Current Client Processing Time |
Amount of time taken to execute the servlet during the last interval |
Active Invocations |
Number of active invocations |
Active Sessions |
Number of active sessions of the application |
Active Response Time |
Average execution time of the application. The average response time of an application is calculated by dividing the number of active requests generated between two consecutive time intervals (that is, the time when the agent collects the data from the server), by the time taken for processing these requests. |
Total Time |
Time taken to execute all invocations of the servlet from the time of its creation |
This category of metrics provides information about the active JDBC connections. The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.This category of metrics provides information about the data source. The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.This category of metrics provides information about deployment tasks. The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.Table 2-4 Deployment Task Metrics
Metric | Description |
---|---|
Application Name |
Name of the application that is to be deployed |
Begin Time |
Time when the deployment was started |
End Time |
Time when the deployment was completed |
Running |
Number of deployments that are in the running state |
Status |
Status of the deployment task |
The details provided by this category of metrics can be used to monitor a BEA WebLogic Server Domain. A domain can contain zero or more clusters. The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.This category of metrics provides information about the EJB cache. The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.Table 2-6 EJB Cache Metrics
Metric | Description |
---|---|
Activation Count |
Name of the current cluster target for a deployment |
Cache Access Count |
Number of times the cache has been accessed |
Cache Hit Count |
Number of times the cache has been hit |
Cache Miss Count |
Total number of times an attempt to access a bean from the cache failed. This information is useful for determining the effectiveness of the EJB cache. |
Cached Beans Current Count |
Total number of EJB instances currently in the cache |
Passivation Count |
Total number of EJBs that have been passivated |
This category of metrics is a top-level interface for configuration information that Server maintains for EJB module. The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.Table 2-7 EJB Component Config Metrics
Metric | Description |
---|---|
Caching Disabled |
A private property that disables caching in proxies |
Keep Generated |
Should be true if you want EJBC to keep its generated source files, and false if you want EJBC to delete them after compiling |
Persistence Enabled |
Sets the persistenceEnabled attribute of the ConfigurationMBean object |
URI |
Returns a URI pointing to the application component, usually on the Administration Server |
This category of metrics is a top level interface for all runtime information collected for an EJB module. The following table lists the metrics and associated descriptions.
This category of metrics contains accessory methods for all free pool runtime information for an EJB. The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.Table 2-9 EJB Pool Metrics
Metric | Description |
---|---|
Access Total Count |
Total number of times an attempt was made to get a bean instance from the free pool |
Beans In Use Count |
Total number of bean instances currently in use from the free pool |
Beans In Use Current Count |
Number of bean instances currently being used from the free pool |
Destroyed Total Count |
Number of times a bean from the free pool was destroyed as non-application exceptions were thrown from it |
Idle Beans Count |
Total number of available bean instances in the free pool |
Miss Total Count |
Number of times a failed attempt was made to get an instance from the free pool |
Pooled Beans Current Count |
Number of bean instances in the free pool that are currently available |
Waiter Current Count |
Number of threads currently waiting for an available bean instance from the pool |
Waiter Total Count |
Total number of threads currently waiting for an available bean instance from the free pool |
This category of metrics provides runtime information about all EJB transactions. The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.Table 2-10 EJB Transaction Metrics
Metric | Description |
---|---|
Transactions Committed Total Count |
Total number of transactions that were committed |
Transactions RolledBack Total Count |
Total number of transactions that were rolled back |
Transactions TimedOut Total Count |
Total number of transactions that were timed out |
The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.The details provided by this category of metrics can be used to configure an execute queue and its associated thread pool. The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.Table 2-12 Execute Queue Config Metrics
Metric | Description |
---|---|
Queue Length |
Sets the queueLength attribute of the ExecuteQueueMBean object |
Queue Length Threshold Percent |
Indicates the threshold value (in percentage) for the length of this queue, set in QueueLength |
Thread Count |
Sets the threadCount attribute of the ExecuteQueueMBean object |
Thread Priority |
Indicates the priority of the threads associated with this queue |
Threads Increase |
Indicates the number of threads to grow when a queue is within QueueLengthThresholdPercent of the set QueueLength |
Threads Maximum |
Indicates the maximum number of threads this execute queue can have |
Threads Minimum |
Indicates the minimum number of threads in the pool |
The details provided by this category of metrics can be used to configure an execute queue and its associated thread pool. The following table lists the metrics and associated descriptions.
This category of metrics provides runtime information about the application. The following table lists the metrics and associated descriptions.
This category of metrics provides information about the J2EE server. The following table lists the metrics and associated descriptions.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.