|
Oracle® Enterprise Manager Metric Reference Manual
10g Release 1 (10.1) Part No. B12015-01 |
|
|
|
|
The Oracle Enterprise Manager Grid Control Console can be used to manage Oracle Application Server Containers for J2EE (OC4J). You can use the All Metrics page for an OC4J target in the Oracle Enterprise Manager Grid Control Console to view the metrics that have been collected for that target by the Oracle Management Agent.
Metrics for applications within the OC4J instance.
This metric is for internal use only.
This metric is for internal use only.
This metric is for internal use only.
This metric is for internal use only.
This metric is for internal use only.
The number of servlets and JSPs executed by this application since startup.
The total amount of time it took to execute EJB methods for this application.
The total number of times that EJB methods were invoked for this application.
The total amount of time it took to execute servlets and JSPs for this application.
The total amount of time it took to execute servlets, JSPs, and EJB methods for this application.
Metrics for all OC4J instances.
The number of active HTTP sessions used by all OC4J instances in the application server.
The average amount of time it took to execute servlets and JSPs for all OC4J instances in the application server during a recent interval. The interval is the period of time specified as the collection frequency for this metric.
The rate at which servlets and JSPs are being invoked for all OC4J instances in the application server during a recent interval. The interval is the period of time specified as the collection frequency for this metric.
Metrics for the application.
The number of EJB methods that are currently being executed by this application.
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-1 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% |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The number of servlets and JSPs currently being executed by this application.
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 number of active servlets and JSPs for application %name% is %value% |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The number of active HTTP sessions used by the application.
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-3 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% |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The rate at which EJB methods are currently being executed by this application.
The time it took to execute EJB methods for this application over a recent interval. The interval is the period of time specified as the collection frequency for this metric.
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 average execution time for an EJB method for application %name% is %value% seconds |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The average amount of time it took 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.
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 average processing time for a servlet or JSP for application %name% is %value% seconds |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The 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.
Metrics for EJBs.
The number of EJB methods that are currently being executed for this EJB.
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 EJB methods for EJB %name%, EJB module %oc4j_ejb_module%, application %oc4j_ear% is %value% |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The rate at which 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.
The time it took 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.
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 EJB %name%, EJB module %oc4j_ejb_module%, application %oc4j_ear% is %value% seconds |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
Metrics for EJB modules.
The number of EJB methods that are currently being executed by this EJB module.
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 number of active EJB methods for EJB module %name%, application %oc4j_ear% is %value% |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The rate at which 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.
The time it took 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.
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-9 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 |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
Metrics for the OC4J instance.
The number of EJB methods that are currently being executed by this OC4J instance.
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-10 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% |
The number of servlets and JSPs currently being executed by this OC4J instance.
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-11 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% |
The number of active HTTP sessions used by the OC4J instance.
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 sessions is %value% |
The number of transactions that are currently open for this OC4J instance.
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 number of active transactions is %value% |
The rate at which 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.
The time it took to execute EJB methods for this OC4J instance over a recent interval. The interval is the period of time specified as the collection frequency for this metric.
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-14 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 |
The amount of heap space used by the OC4J instance.
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 | Heap Usage is %value%MB |
The number of JDBC connections open by applications that are part of the OC4J instance.
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 number of active JDBC connections is %value% |
The average amount of time it took 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.
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-17 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 |
The 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.
The time that the OC4J instance was started. It is represented in milliseconds since the Unix epoch.
The Unix epoch is January 1, 1970.
Metrics for JSPs.
Indicates whether or not this JSP is multi-threaded. The value of this metric will be either TRUE or FALSE.
The number of active instances of this JSP.
STM means single threaded model. This metric is only for single threaded JSPs, not multi-threaded JSPs.
The number of clients that are currently executing this JSP.
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 %name% JSPs for web module %oc4j_web_module%, application %oc4j_ear% is %value% |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The number of available instances to execute this JSP.
STM means single threaded model. This metric is only for single threaded JSPs, not multi-threaded JSPs.
The total time spent executing the client code for this JSP since this OC4J instance was started.
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 average processing time for JSP %name%, web module %oc4j_web_module%, application %oc4j_ear% is %value% seconds |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The 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.
Metrics for servlets.
The number of clients that are currently executing this servlet.
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 %name% servlets for web module %oc4j_web_module%, application %oc4j_ear% is %value% |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The average amount of time it took 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.
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 average processing time for servlet %name%, web module %oc4j_web_module%, application %oc4j_ear% is %value% seconds |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The 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.
Metrics for OC4J web modules.
The number of servlets and JSPs currently being executed by this web module.
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 number of active servlets and JSPs for web module %name%, application %oc4j_ear% is %value% |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The number of active HTTP sessions used by this web module.
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 | The number of active sessions for web module %name%, application %oc4j_ear% is %value% |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The average time 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.
The 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.
The average amount of time it took 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.
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 average processing time for a servlet or JSP for web module %name%, application %oc4j_ear% is %value% seconds |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
Metrics for OC4J instance resource usage.
The percentage of idle CPU time.
The percentage of the CPU time used by the OC4J instance.
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 | CPU Utilization is %value%%% |
The percentage of memory available.
The amount of free memory on the system.
The percentage of memory used by the OC4J instance.
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-26 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%%% |
The amount of memory used by the OC4J instance.
Shows the percentage of the CPU owned and used by 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.
This metric shows the percentage of host memory in use by processes and applications other than the OC4J instance. If you are having problems with memory usage on the OC4J host computer, this metric can help you determine whether or not the OC4J instance is causing the problem.
Shows the physical memory usage (in MB) by processes and applications other than the OC4J instance. If you are having problems with memory usage on the OC4J host computer, this metric can help you determine whether or not the OC4J instance is causing the problem.
Response metrics for OC4J.
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.
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 Minute | After Every 60 Samples | =
|
Not Defined | 0 | 1 | The OC4J instance is down |