Oracle® Enterprise Manager Oracle Application Server Metric Reference Manual 10g Release 2 (10.2) Part Number B25987-01 |
|
|
View PDF |
Enterprise Manager can be used to manage Oracle Application Server Containers for J2EE (OC4J). You can use the All Metrics page for an OC4J target to view the metrics that have been collected for that target by the Oracle Management Agent.
This metric category provides metrics for all the OC4J instances of an application server.
Note: For all target versions, the collection frequency for each metric is every 5 minutes. |
The following table lists the metrics and their associated descriptions.
Table 11-1 OC4J All Instances Metrics
Metric | Description |
---|---|
Active Sessions |
Number of HTTP sessions used by all the OC4J instances of this application server. |
Request Processing Time (seconds) |
|
Requests Per Second |
Rate at which servlets and JSPs are being invoked for all the OC4J instances of this application server, during a recent interval. The interval is the period of time specified as the collection frequency for this metric |
This metric shows the average amount of time it consumed to execute servlets and JSPs for all the OC4J instances of this application server, during a recent interval. The interval is the period of time specified as the collection frequency for this metric.
Metric Summary
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.
Table 11-2 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The average processing time for a servlet or JSP is %value% seconds |
This metric category provides metrics for the application.
Note: For all target versions, the collection frequency for each metric is every 5 minutes. |
The following table lists the metrics and their descriptions.
Table 11-3 OC4J Application Metrics
Metric | Description |
---|---|
Active EJB Methods |
|
Active Requests |
|
Active Sessions |
|
EJB Method Execution Rate (per second) |
Rate at which EJB methods are currently being executed by this application |
EJB Method Execution Time (seconds) |
|
Request Processing Time (seconds) |
|
Requests Per Second |
Rate at which servlets and JSPs are being invoked for this application during a recent interval. The interval is the period of time specified as the collection frequency for this metric. |
This metric shows the number of EJB methods that are currently being executed by this application.
Metric Summary
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.
Table 11-4 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active EJB methods for application %name% is %value% |
Multiple Thresholds
If warning or critical threshold values are currently set for any "Application Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
For this metric you can set different warning and critical threshold values for each "Application Name" object.
To specify or change warning or critical threshold values for each "Application Name" object, use the Edit Thresholds page.
This metric shows the number of servlets and JSPs currently being executed by this application.
Metric Summary
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.
Table 11-5 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active servlets and JSPs for application %name% is %value% |
Multiple Thresholds
If warning or critical threshold values are currently set for any "Application Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
For this metric you can set different warning and critical threshold values for each "Application Name" object.
To specify or change warning or critical threshold values for each "Application Name" object, use the Edit Thresholds page.
This metric shows the number of active HTTP sessions used by the application.
Metric Summary
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.
Table 11-6 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active sessions for application %name% is %value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Application Name" object.
If warning or critical threshold values are currently set for any "Application Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Application Name" object, use the Edit Thresholds page.
This metric shows the time consumed to execute EJB methods for this application during a recent interval. The interval is the period of time specified as the collection frequency for this metric.
Metric Summary
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.
Table 11-7 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The average execution time for an EJB method for application %name% is %value% seconds |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Application Name" object.
If warning or critical threshold values are currently set for any "Application Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Application Name" object, use the Edit Thresholds page.
This metric shows the average time consumed to execute servlets and JSPs from this application during a recent interval. The interval is the period of time specified as the collection frequency for this metric.
Metric Summary
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.
Table 11-8 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The average processing time for a servlet or JSP for application %name% is %value% seconds |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Application Name" object.
If warning or critical threshold values are currently set for any "Application Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Application Name" object, use the Edit Thresholds page.
This metric category provides metrics for datasources.
The following table lists the metrics and their associated descriptions.
Table 11-9 OC4J Datasource Metrics
Metric | Description |
---|---|
Active JDBC Connections |
Number of JDBC connections currently open for this datasource. |
Available Cached Connections |
Number of unused connections in the cache for this datasource |
Connection Cache Hit Rate (%) |
Percentage of time the datasource was able to get a connection from the cache (as opposed to having to create a new one) |
Statement Cache Hit Rate (%) |
Percentage of time the datasource was able to get a statement from the cache (as opposed to having to create a new one) during the last 5 minutes |
This metric category provides metrics for EJB Methods.
The following table lists the metrics and their associated descriptions.
Table 11-10 OC4J EJB Method Metrics
Metric | Description |
---|---|
Active Methods |
Number of times this method is being executed right now |
Client Processing Time (seconds) |
Average time an invocation of this method spent in client code during the last 5 minutes |
Method Execution Rate (per second) |
Number of times per second this method has been executed during the last 5 minutes |
Overhead Time (seconds) |
Average time an invocation of this method spent in wrapper code during the last 5 minutes |
This metric category provides metrics for EJBs.
Note: For all target versions, the collection frequency for each metric is every 5 minutes. |
The following table lists the metrics and their associated descriptions.
Table 11-11 OC4j EJB Metrics
Metric | Description |
---|---|
Active Methods |
|
Method Execution Time (seconds) |
Rate at which the EJB methods are currently being executed for this EJB during a recent interval. The interval is the period of time specified as the collection frequency for this metric. |
Method Execution Time (seconds) |
|
Type of EJB |
Type of the EJB (i.e. Entity type or Session type). |
This metric shows the number of EJB methods that are currently being executed for this EJB.
Metric Summary
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.
Table 11-12 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active EJB methods for EJB %name%, EJB module %oc4j_ejb_module%, application %oc4j_ear% is %value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "EJB Name", "EJB Module Name", and "Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "EJB Name", "EJB Module Name", and "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 "EJB Name", "EJB Module Name", and "Application Name" objects, use the Edit Thresholds page.
This metric shows the time consumed to execute EJB methods for this EJB during a recent interval. The interval is the period of time specified as the collection frequency for this metric.
Metric Summary
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.
Table 11-13 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The average execution time for an EJB method for EJB %name%, EJB module %oc4j_ejb_module%, application %oc4j_ear% is %value% seconds |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "EJB Name", "EJB Module Name", and "Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "EJB Name", "EJB Module Name", and "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 "EJB Name", "EJB Module Name", and "Application Name" objects, use the Edit Thresholds page.
This metric category provides metrics for EJB modules.
The following table lists the metrics and their associated descriptions.
Table 11-14 OC4j EJB Module Metrics
Metric | Description |
---|---|
Active Methods |
|
Method Execution Rate |
Rate at which the EJB methods are currently being executed for this EJB module during a recent interval. The interval is the period of time specified as the collection frequency for this metric. For all target versions, the collection frequency for this metric is every 5 minutes. |
Method Execution Time (seconds) |
This metric shows the number of EJB methods that are currently being executed by this EJB module.
Metric Summary
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.
Table 11-15 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active EJB methods for EJB module %name%, application %oc4j_ear% is %value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "EJB Module Name" and "Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "EJB Module Name" and "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 "EJB Module Name" and "Application Name" objects, use the Edit Thresholds page.
This metric shows the time consumed to execute EJB methods for this EJB module during a recent interval. The interval is the period of time specified as the collection frequency for this metric.
Metric Summary
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.
Table 11-16 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The average execution time for an EJB method for EJB module %name%, application %oc4j_ear% is %value% seconds |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "EJB Module Name" and "Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "EJB Module Name" and "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 "EJB Module Name" and "Application Name" objects, use the Edit Thresholds page.
This metric category provides metrics for the OC4J instance.
Note: For all target versions, the collection frequency for each metric is every 5 minutes. |
The following table lists the metrics and their associated descriptions.
Table 11-17 OC4J Instance Metrics
Metric | Description |
---|---|
Active EJB Methods |
|
Active Requests |
|
Active Sessions |
|
Active Transactions |
Section 11.7.4, "Active Transactions" |
EJB Method Execution Rate (per second) |
Rate at which the EJB methods are currently being executed by this OC4J instance during a recent interval. The interval is the period of time specified as the collection frequency for this metric. |
EJB Method Execution Time (seconds) |
|
Heap Usage (MB) |
Section 11.7.6, "Heap Usage (MB)" |
Open JDBC Connections |
Section 11.7.7, "Open JDBC Connections" |
Request Processing Time (seconds) |
Section 11.7.8, "Request Processing Time (seconds)" |
Requests Per Second |
Rate at which servlets and JSPs are being invoked for this OC4J instance during a recent interval. The interval is the period of time specified as the collection frequency for this metric. |
Start Time (ms since Epoch) |
Time when the OC4J instance was started. It is represented in milliseconds since the UNIX epoch (i.e. January 1, 1970) |
This metric shows the number of EJB methods that are currently being executed by this OC4J instance.
Metric Summary
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.
Table 11-18 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active EJB methods is %value% |
This metric shows the number of servlets and JSPs currently being executed by this OC4J instance.
Metric Summary
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.
Table 11-19 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active servlets and JSPs is %value% |
This metric shows the number of active HTTP sessions used by the OC4J instance.
Metric Summary
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.
Table 11-20 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active sessions is %value% |
This metric shows the number of transactions that are currently open for this OC4J instance.
Metric Summary
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.
Table 11-21 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active transactions is %value% |
This metric shows the time consumed to execute EJB methods for this OC4J instance during a recent interval. The interval is the period of time specified as the collection frequency for this metric.
Metric Summary
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.
Table 11-22 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The average execution time for an EJB method is %value% seconds |
This metric shows the amount of heap space used by the OC4J instance.
Metric Summary
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.
Table 11-23 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
Heap Usage is %value%MB |
This metric shows the number of JDBC connections open by applications that are part of the OC4J instance.
Metric Summary
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.
Table 11-24 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active JDBC connections is %value% |
This metric shows the average time consumed to execute servlets and JSPs for this OC4J instance during a recent interval. The interval is the period of time specified as the collection frequency for this metric.
Metric Summary
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.
Table 11-25 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The average processing time for a servlet or JSP is %value% seconds |
This metric category provides metrics for JSPs.
Note: For all target versions, the collection frequency for each metric is every 5 minutes. |
The following table lists the metrics and their associated descriptions.
Table 11-26 OC4J JSP Metrics
Metric | Description |
---|---|
Is multi-threaded? |
Indicates whether or not this JSP is multi-threaded. The value of this metric is either TRUE or FALSE |
Active Instances (STM only) |
Number of active instances of this JSP. STM means Single Threaded Model. This metric is only for single threaded JSPs, and not for multi-threaded JSPs. |
Active Requests |
|
Available Instances (STM only) |
Number of available instances to execute this JSP |
Client Processing Time (seconds) |
|
Requests Per Second |
Rate at which this JSP has been invoked by clients during a recent interval. The interval is the period of time specified as the collection frequency for this metric |
This metric shows the number of clients that are currently executing this JSP.
Metric Summary
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.
Table 11-27 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active %name% JSPs for web module %oc4j_web_module%, application %oc4j_ear% is %value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "JSP Name", "Web Module Name", and "Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "JSP Name", "Web Module Name", and "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 "JSP Name", "Web Module Name", and "Application Name" objects, use the Edit Thresholds page.
This metric shows the total time spent executing the client code for this JSP since this OC4J instance was started.
Metric Summary
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.
Table 11-28 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The average processing time for JSP %name%, web module %oc4j_web_module%, application %oc4j_ear% is %value% seconds |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "JSP Name", "Web Module Name", and "Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "JSP Name", "Web Module Name", and "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 "JSP Name", "Web Module Name", and "Application Name" objects, use the Edit Thresholds page.
This metric category provides metrics for OC4J JVMs.
Note: For all target versions, the collection frequency for each metric is every 5 minutes. |
The following table lists the metrics and their associated descriptions.
Table 11-29 OC4J JVM Metrics
Metric | Description |
---|---|
Island Name |
Name of the island that the JVM is using |
Active EJB Methods |
|
Active Requests |
|
Active Threads |
|
CPU Usage (%) |
|
Heap Usage (MB) |
|
Memory Usage (MB) |
|
Start Time (ms since Epoch) |
Time when the JVM was started |
This metric shows the number of EJB methods currently being executed in the JVM.
Metric Summary
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.
Table 11-30 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active EJB methods is %value% for process %pid.value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "PID" object.
If warning or critical threshold values are currently set for any "PID" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "PID" object, use the Edit Thresholds page.
This metric shows the number of servlet/JSP requests currently being processed in the JVM.
Metric Summary
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.
Table 11-31 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active servlets and JSPs is %value% for process %pid.value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "PID" object.
If warning or critical threshold values are currently set for any "PID" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "PID" object, use the Edit Thresholds page.
This metric shows the number of threads currently executing in the JVM.
Metric Summary
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.
Table 11-32 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
There are %value% active threads for process %pid.value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "PID" object.
If warning or critical threshold values are currently set for any "PID" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "PID" object, use the Edit Thresholds page.
This metric shows the percentage of CPU time used by the JVM.
Metric Summary
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.
Table 11-33 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
CPU Utilization is %value%%% for process %pid.value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "PID" object.
If warning or critical threshold values are currently set for any "PID" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "PID" object, use the Edit Thresholds page.
This metric shows the amount of heap space used by the JVM.
Metric Summary
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.
Table 11-34 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
Heap Usage is %value% MB for process %pid.value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "PID" object.
If warning or critical threshold values are currently set for any "PID" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "PID" object, use the Edit Thresholds page.
This metric shows the amount of physical memory used by the JVM.
Metric Summary
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.
Table 11-35 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
Memory Utilization is %value% MB for process %pid.value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "PID" object.
If warning or critical threshold values are currently set for any "PID" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "PID" object, use the Edit Thresholds page.
This metric category provides metrics for servlets.
The following table lists the metrics and their associated descriptions.
Table 11-36 OC4J Servlet Metrics
Metric | Description |
---|---|
Active Requests |
|
Client Processing Time |
|
Requests Per SEcond |
Rate at which the servlet has been invoked by clients during a recent interval. The interval is the period of time specified as the collection frequency for this metric. For all target versions, the collection frequency for this metric is every 5 minutes. |
This metric shows the number of clients that are currently executing this servlet.
Metric Summary
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.
Table 11-37 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active %name% servlets for web module %oc4j_web_module%, application %oc4j_ear% is %value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Servlet Name", "Web Module Name", and "Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "Servlet Name", "Web Module Name", and "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 "Servlet Name", "Web Module Name", and "Application Name" objects, use the Edit Thresholds page.
This metric shows the average time consumed to execute the client code for this servlet during a recent interval. The interval is the period of time specified as the collection frequency for this metric.
Metric Summary
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.
Table 11-38 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The average processing time for servlet %name%, web module %oc4j_web_module%, application %oc4j_ear% is %value% seconds |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Servlet Name", "Web Module Name", and "Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "Servlet Name", "Web Module Name", and "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 "Servlet Name", "Web Module Name", and "Application Name" objects, use the Edit Thresholds page.
This metric category provides metrics for the OC4J web modules.
Note: For all target versions, the collection frequency for each metric is every 5 minutes. |
The following table lists the metrics and their associated descriptions.
Table 11-39 OC4J Web Module Metrics
Metric | Description |
---|---|
Active Requests |
|
Active Sessions |
Section 11.11.2, "Active Sessions" |
Class Load Time (seconds) |
Average time consumed to load the classes for this web module during the last interval. The interval is the period of time specified as the collection frequency for this metric. |
Client Time (seconds) |
Average time spent executing client code for this web module during the last interval. The interval is the period of time specified as the collection frequency for this metric. |
Request Processing Time (seconds) |
|
Requests Per Second |
Number of servlets and JSPs processed by this web module since this OC4J instance was started |
This metric shows the number of servlets and JSPs currently being executed by this web module.
Metric Summary
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.
Table 11-40 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active servlets and JSPs for web module %name%, application %oc4j_ear% is %value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Web Module Name" and "Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "Web Module Name" and "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 "Web Module Name" and "Application Name" objects, use the Edit Thresholds page.
This metric shows the number of active HTTP sessions used by this web module.
Metric Summary
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.
Table 11-41 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The number of active sessions for web module %name%, application %oc4j_ear% is %value% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Web Module Name" and "Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "Web Module Name" and "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 "Web Module Name" and "Application Name" objects, use the Edit Thresholds page.
This metric shows the average time consumed to execute servlets and JSPs for this web module during a recent interval. The interval is the period of time specified as the collection frequency for this metric.
Metric Summary
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.
Table 11-42 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
The average processing time for a servlet or JSP for web module %name%, application %oc4j_ear% is %value% seconds |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Web Module Name" and "Application Name" objects.
If warning or critical threshold values are currently set for any unique combination of "Web Module Name" and "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 "Web Module Name" and "Application Name" objects, use the Edit Thresholds page.
This metric category provides metrics for the OC4J instance resource usage.
Note: For all target versions, the collection frequency for each metric is every 5 minutes. |
The following table lists the metrics and their associated descriptions.
Table 11-43 OC4J Resource Usage Metrics
Metric | Description |
---|---|
CPU Idle Time (%) |
Percentage of CPU idle time |
CPU Usage (%) |
|
Free Memory (%) |
Percentage of physical memory available. For target versions 9.0.2.x and 9.0.3.x, the collection frequency is every 5 minutes. |
Free Memory (MB) |
Amount of free physical memory on the system |
Memory Usage (%) |
Percentage of physical memory used by the OC4J instance. For target versions 9.0.2.x and 9.0.3.x, the collection frequency is every 5 minutes. |
Memory Usage (MB) |
Amount of physical memory used by the OC4J instance |
Other CPU Usage (%) |
Percentage of CPU owned and used by the host processes other than the OC4J instance. If you are having problems with CPU usage on the OC4J host computer, this metric can help you determine whether or not the OC4J instance is causing the problem. |
Other Memory Usage (%) |
Percentage of host memory used by processes and applications other than the OC4J instance. If you are having problems with physical memory usage on the OC4J host computer, this metric can help you determine whether or not the OC4J instance is causing the problem. For target versions 9.0.2.x and 9.0.3.x, the collection frequency is every 5 minutes. |
Other Memory Usage (MB) |
Physical memory used (in MB) by processes and applications other than the OC4J instance. If you are having problems with physical memory usage on the OC4J host computer, this metric can help you determine whether or not the OC4J instance is causing the problem. |
Total Memory (MB) |
Total amount of physical memory available.For target versions 9.0.2.x and 9.0.3.x, the collection frequency is every 5 minutes. |
This metric shows the percentage of CPU time used by the OC4J instance.
Metric Summary
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.
Table 11-44 Metric Summary Table
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 12 Samples |
> |
Not Defined |
Not Defined |
2 |
CPU Utilization is %value%%% |
This metric shows the percentage of physical memory used by the OC4J instance.
Metric Summary
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.
Table 11-45 Metric Summary Table
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 12 Samples |
> |
80 |
90 |
2 |
Memory Utilization is %value%%% |
This metric category provides response metrics for OC4J.
This metric shows whether the OC4J server is up or down. If the value is 1, OC4J is up. If the value is 0, it is down.
Metric Summary
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.
Table 11-46 Metric Summary Table
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 OC4J instance is down |