| Oracle® Enterprise Manager Oracle Application Server Metric Reference Manual 10g Release 2 (10.2) Part Number B25987-01 |
|
|
View PDF |
| Oracle® Enterprise Manager Oracle Application Server Metric Reference Manual 10g Release 2 (10.2) Part Number B25987-01 |
|
|
View PDF |
Oracle Enterprise Manager gathers performance metrics that provide high-level information about the status, performance, and availability of your Oracle Application Server.
This category of metrics uses the Application URL to measure the responsiveness and availability of the application server instance.
The Application URL Response Time is measured by automatically and continuously attempting to access the Application URL. The response time includes the time it takes to access the URL and for the application server to render and display the Application URL content.
Note that this metric is used primarily by Grid Control to measure the responsiveness of the application server instance. The Application URL is shown in the General section of the Application Server Home page in the Grid Control Console, and it is used to generate the Application URL Response chart on that page.
By the default, the Application URL consists of the application server host name and default listener port for the Oracle HTTP Server component. For example: http://hostname.domain:7778.
If you are using the Grid Control Console, you can modify the Application URL by modifying the properties of the Application Server target. Alternatively, you can change the Application URL by clicking Change Application URL on the Application Server Home page in the Grid Control Console.
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 13-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 average response time for the application URL is %value% seconds |
User Action
If you are using Grid Control, and the response time of the Availability URL exceeds the threshold, investigate other related performance metrics, such as the application server Resource Usage metrics, to review the load on the host computer. Also, check for alerts that may have been generated by specific application server components, such as the HTTP Server instance, OC4J instances, or the host computer.
This metric indicates whether or not the Application URL, which is used to define the responsiveness of the Application Server, can be accessed successfully. For example, if the Application URL returns an error, the Application URL Status metric will be down.
Note that this metric is used primarily by Grid Control to measure the responsiveness of the application server instance. The Application URL is shown in the General section of the Application Server Home page in the Grid Control Console, and it is used to generate the Application URL Response chart on that page.
A value of one (1) indicates that the Oracle Management Agent can access the Application URL; a value of zero (0) indicates that the Application URL cannot be accessed successfully.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
If the Application URL Status is down, first verify that the Application URL is a valid URL that can be used to measure the availability and responsiveness of the application server instance. If it is a valid URL, especially one that was available previously, the down status indicates that the Oracle HTTP Server for the instance is now unavailable and unable to render the Application URL.
The OPMN Process Information Metrics provide you with a snapshot of how the primary components of your application server--as well as specific components of Oracle Enterprise Manager--are performing. The list provided here will vary, depending upon the application server components you have installed and configured for this instance of Oracle Application Server.
Enterprise Manager components that you can monitor by reviewing the OPMN Process Information Metrics include the Oracle Management Agent (agent), the Oracle Application Server Control process (console), and the Oracle Management Agent watchdog process (watchdog).
This metric represents the percentage of host CPU used by the selected application server component.
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 13-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 |
|---|---|---|---|---|---|---|---|
|
9.0.4.x |
Every 5 Minutes |
After Every 12 Samples |
> |
Not Defined |
Not Defined |
2 |
CPU Utilization of %name% is %value%%% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Component Name" object.
If warning or critical threshold values are currently set for any "Component 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 "Component Name" object, use the Edit Thresholds page.
User Action
You can use this metric to determine which components are using the most CPU on your system. If one or more components are consuming a large amount of CPU, consider changing the component configuration settings to reduce the amount of CPU consumption.
This metric represents the percentage of host memory used by the selected application server component.
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 13-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 |
|---|---|---|---|---|---|---|---|
|
9.0.4.x |
Every 5 Minutes |
After Every 12 Samples |
> |
80 |
90 |
2 |
Memory Utilization of %name% is %value%%% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Component Name" object.
If warning or critical threshold values are currently set for any "Component 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 "Component Name" object, use the Edit Thresholds page.
User Action
You can use this metric to determine which components are using the most memory on your system. If one or more components are consuming a large amount of memory, consider changing the component configuration settings to reduce the amount of memory consumption.
This metric represents the memory usage in megabytes for the selected component.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| 9.0.4.x | Every 5 Minutes |
User Action
You can use this metric to determine which components are using the most memory on your system. If one or more components are consuming a large amount of memory, consider changing the component configuration settings to reduce the amount of memory consumption.
This metric is for internal use only.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| 9.0.4.x | Every 5 Minutes |
This metric is for internal use only.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| 9.0.4.x | Every 5 Minutes |
This metric indicates whether the component is up or down. A value of one (1) indicates that the component is up and running; a value of zero (0) indicates that the component is down.
If you are using Grid Control, see the "About Availability" topic in the online help for more information about how Enterprise Manager determines the availability of an Oracle Application Server or Enterprise Manager component,
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| 9.0.4.x | Every 5 Minutes |
This metric shows you the percentage of memory that is free on the application server host. The amount of free memory available can help you determine whether or not the system is ready to handle a heavier load.
Note: You can view the value of this metric for each of the application server components. However, the value of this metric applies to the memory for the host where the application server is running. As a result, the value is the same for all the components that are running on the host.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| 9.0.4.x | Every 5 Minutes |
User Action
If the percentage of Free Memory is low, compare this metric value to Component Memory Usage (%), which shows the percentage of memory used by each of the application server components. You can then identify which components are using the most memory on the system.
To troubleshoot memory issues, check the list of top processes to determine which system processes are using the most memory. This value is also available on the Host home page. To obtain more detailed hardware information about the host computer, see one of the following help topics:
If you are using Grid Control, see the "Viewing Host Target Overview Information" topic.
If you are using Application Server Control, see the "Obtaining Information about the Host Computer" topic.
This metric shows you the amount of memory (in megabytes) that are free on the application server host. The amount of free memory available can help you determine whether or not the system is ready to handle a heavier load.
Note: You can view the value of this metric for each of the application server components. However, the value of this metric applies to the memory for the host where the application server is running. As a result, the value is the same for all the components that are running on the host.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| 9.0.4.x | Every 5 Minutes |
User Action
Compare to "Component Memory Usage (MB)", which shows the amount of memory being used by the various components on the host. This can help you identify which components are using the most memory.
In addition, check the list of top processes to determine which system processes are using the most memory. This value is also available on the Host home page. To obtain more detailed hardware information about the host computer, see one of the following topics in the online help:
If you are using Grid Control, see the "Viewing Host Target Overview Information" topic.
If you are using Application Server Control, see the "Obtaining Information about the Host Computer" topic.
This metric represents the percentage of time that the CPU was idle and the system did not have an outstanding disk I/O request.
Note: You can view the value of this metric for each of the application server components. However, the value of this metric applies to the memory for the host where the application server is running. As a result, the value is the same for all the components that are running on the host.
You can also review the CPU Idle time for the host target. For more information, navigate to the Host home page and click the appropriate link to view all the metrics for the host target.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| 9.0.4.x | Every 5 Minutes |
User Action
If the amount of idle CPU is low, review the Component CPU Usage (%) metric to identify which application server components are consuming the most CPU.
In addition, check the Other CPU Usage (%) metric to determine if other processes, besides those of the application server, are using large amounts of CPU.
This metric shows you the total physical memory available on the application server host computer.
Note: You can view the value of this metric for each of the application server components. However, the value of this metric applies to the memory for the host where the application server is running. As a result, the value is the same for all the components that are running on the host.
This value is also available on the Host home page. To obtain more detailed hardware information about the host computer, see one of the following help topics:
If you are using Grid Control, see the "Viewing Host Target Overview Information" topic.
If you are using Application Server Control, see the "Obtaining Information about the Host Computer" topic.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| 9.0.4.x | Every 5 Minutes |
This category of metrics provides you with information about the CPU and Memory being used by the application server.
This metric shows the percentage of system CPU time that is idle. The amount of idle CPU time can help you determine whether or not the system is ready to handle a heavier load.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
If the amount of idle CPU is low, review the Component CPU Usage (%) metric to identify which application server components are consuming the most CPU.
In addition, check the Other CPU Usage (%) metric to determine if other processes, besides those of the application server, are using large amounts of CPU.
Use this metric to determine the percentage of the host CPU being used by the application server and all its configured and enabled components.
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 13-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 |
> |
70 |
75 |
2 |
CPU Utilization is %value%%% |
User Action
If you are using Grid Control and the CPU Usage for the application server exceeds the alert threshold, check the individual application server components to see if a particular component is consuming excessive amounts of CPU. For more information, see 'Viewing the Performance of Your Application Server' topic in the Grid Control online help. Also, check for alerts that may have been generated by specific application server components, such as the HTTP Server instance, OC4J instances, or the host computer.
Navigate to the host home page and review the top processes to see if you can identify which processes are consuming the most CPU. For more information, see the following topics in the online help:
If you are using Grid Control, see the "Viewing Host Target Overview Information" topic.
If you are using Application Server Control, see the "Obtaining Information about the Host Computer" topic.
This metric shows you the percentage of memory that is free on the application server host. The amount of free memory available can help you determine whether or not the system is ready to handle a heavier load.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
Compare to Component Memory Usage (%) to determine which application server components are using the most memory. Unlike the Free Memory (%) Metric, you can set thresholds for the Component Memory Usage (%) and Memory Usage (%) metrics and be alerted when they exceed the threshold.
To troubleshoot memory issues, you can also check the list of top processes to determine which system processes are using the most memory. To obtain more detailed hardware information about the host computer, see one of the following in the online help:
If you are using Grid Control, see the "Viewing Host Target Overview Information" topic.
If you are using Application Server Control, see the "Obtaining Information about the Host Computer" topic.
This metric shows you the amount of memory (in megabytes) that are free on the application server host. The amount of free memory available can help you determine whether or not the system is ready to handle a heavier load.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
If the free memory on the application server host is too low, review the Component Memory Usage (%) metrics to determine which application server components are using the most memory. Unlike the Free Memory (MB) metric, you can set thresholds for the Component Memory Usage (%) and Memory Usage (%) metrics and be alerted when they exceed the threshold.
To troubleshoot memory issues, check the list of top processes to determine which system processes are using the most memory. To obtain more detailed hardware information about the host computer, see one of the following in the online help:
If you are using Grid Control, see the "Viewing Host Target Overview Information" topic.
If you are using Application Server Control, see the "Obtaining Information about the Host Computer" topic.
This metric shows you the percentage of host memory being used by the application server and its configured and enabled components.
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 13-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 |
> |
80 |
90 |
2 |
Memory Utilization is %value%%% |
User Action
To troubleshoot memory issues, check the memory usage of individual application server components and then check the list of top processes to determine which system processes are using the most memory. To obtain more detailed hardware information about the host computer, see one of the following in the online help:
If you are using Grid Control, see the "Viewing Host Target Overview Information" topic.
If you are using Application Server Control, see the "Obtaining Information about the Host Computer" topic.
This metric shows you the amount of memory (in megabytes) being used by the application server and its configured and enabled components.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
Compare this metric with Memory Usage (%), which measures the percentage of host memory being used by the application server. Unlike the Memory Usage (MB) metric, you can set a threshold for the Memory Usage (%) metric and be alerted when it exceeds its threshold.
To troubleshoot memory issues, check the memory usage of individual application server components and then check the list of top processes to determine which system processes are using the most memory. To obtain more detailed hardware information about the host computer, see one of the following in the online help:
If you are using Grid Control, see the "Viewing Host Target Overview Information" topic.
If you are using Application Server Control, see the "Obtaining Information about the Host Computer" topic.
This metric shows the amount of CPU owned and used by host processes, other than the application server and its configured and enabled components. If you are having problems with CPU usage on the application server host computer, this metric can help you determine whether or not the application server is causing the problem.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
Navigate to the host home page and review the top processes to see if you can identify which processes are consuming the most CPU. To obtain more detailed hardware information about the host computer, see one of the following in the online help:
If you are using Grid Control, see the "Viewing Host Target Overview Information" topic.
If you are using Application Server Control, see the "Obtaining Information about the Host Computer" topic.
This metric shows the percentage of host memory in use by other processes or applications, other than the application server and its configured and enabled components. If you are having problems with memory usage on the application server host computer, this metric can help you determine whether or not the application server is causing the problem.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
Navigate to the host home page and review the top processes to see if you can identify which processes are consuming the most memory. To obtain more detailed hardware information about the host computer, see one of the following in the online help:
If you are using Grid Control, see the "Viewing Host Target Overview Information" topic.
If you are using Application Server Control, see the "Obtaining Information about the Host Computer" topic.
This metric shows the amount of memory (in megabytes) currently in use by other processes or applications, other than the application server and its configured and enabled components. If you are having problems with memory usage on the application server host computer, this metric can help you determine whether or not the application server is causing the problem.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
Navigate to the host home page and review the top processes to see if you can identify which processes are consuming the most memory. To obtain more detailed hardware information about the host computer, see one of the following in the online help:
If you are using Grid Control, see the "Viewing Host Target Overview Information" topic.
If you are using Application Server Control, see the "Obtaining Information about the Host Computer" topic.
This category contains the UpDown Status metric, which indicates whether the Application Server is up or down.
This metric indicates whether or not all the enabled Application Server components are up and running. For example, if one OC4J instance is down, the UpDown Status will be down even if the other application server components are up and running. The status of the Application Server appears in the General section of the Application Server home page in the Grid Control Console.
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 13-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 |
0 |
1 |
The application server instance is down |
User Action
If the UpDown Status is down, verify whether the entire application server is down or a subset of the application server components is down. In other words, if one OC4J instance is down, the UpDown status will appear as down, even if the rest of the other application server components are up and running.
If the application server instance is down, you can restart the application server from the Application Server Control Console.
If you are using Grid Control, you can access the Application Server Control Console from the Grid Control Console by clicking Administer on the Application Server home page in the Grid Control Console.
To investigate why the server is down, check for alerts in the Grid Control Console that may have been generated by the application server or by specific server components, such as the HTTP Server instance, OC4J instances, or the host computer.
If you have shut down a particular application server component to save memory, consider disabling the component so its UpDown Status will not affect the overall status of the application server.
