15 Oracle HTTP Server

15.1 Host Metrics

Metrics for the host on which the HTTP Server is running.

15.1.1 Name

This is the host name.

15.2 mod_oc4j Destination Metrics

The metrics in this category provide details about the successful and failed requests routed by mod_oc4j to a particular OC4J Instance. The metrics table shows details such as the OC4J instances to which the requests were routed, the total number of successful and failed requests routed by mod_oc4j to a particular OC4J instance.

The following table lists the metrics and their descriptions.

Note:

For target versions 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 30 minutes.

Table 15-1 mod_oc4j Destination Metrics

Metric	Description
Failover.count, ops	Total number of failovers for this destination
Percentage of Requests that Were Failures	See Section 15.2.1, "Percentage of Requests that Were Failures"
Percentage of Requests that Were Session Requests	Percentage of total number of requests routed by mod_oc4j to this particular OC4J instance that were session requests, during the last collection interval
Requests Per Second Routed to Destination	Number of requests routed per second by mod_oc4j to this particular OC4J instance
Total Failed Requests to Destination	Total number of failed requests routed by mod_oc4j to this particular OC4J instance
Total Successful Requests to Destination	Total number of successful requests routed by mod_oc4j to this particular OC4J instance

15.2.1 Percentage of Requests that Were Failures

The percentage of the total number of requests routed by mod_oc4j to this particular OC4J instance that were failed requests.

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 15-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 and 10.1.2.x	Every 30 Minutes	After Every Sample	>	1	1.5	2	The percentage of requests that resulted in failures is %value%%%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "OC4J Instance Name(s)" object.

If warning or critical threshold values are currently set for any "OC4J Instance Name(s)" 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 "OC4J Instance Name(s)" object, use the Edit Thresholds page.

15.3 mod_oc4j General Metrics

This metric category displays charts that show the count of requests to OC4J instances, and the percentage of requests that failed and resulted in internal errors.

The following table lists the metrics and their descriptions.

Note:

For target versions 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 5 minutes.

Table 15-3 mod_oc4j General Metrics

Metric	Description
Percentage of Request Resulted in Internal Errors	See Section 15.3.1, "Percentage of Requests Resulted in Internal Errors"
Percentage of Requests that Were Failures	Section 15.3.2, "Percentage of Requests that Were Failures"
Percentage of Requests that Were Session Requests	Percentage of total number of requests routed for all the mount points that were session requests, during the last collection interval
Requests Per Second Routed to OC4J Instances	Total number of requests routed per second for all the mount points

15.3.1 Percentage of Requests Resulted in Internal Errors

The percentage of total number of requests routed for all the Mount Points that resulted in internal errors.

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 15-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
9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	1	1.5	2	The percentage of requests that resulted in internal errors is %value%%%

15.3.2 Percentage of Requests that Were Failures

The percentage of total number of requests routed for all the mount points that were failed requests.

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 15-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
9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	1	1.5	2	The percentage of requests that resulted in failures is %value%%%

15.4 mod_oc4j MountPt Metrics

The metrics in this category provide details about the successful and failed requests routed by mod_oc4j for a particular mount point. The metrics table shows details such as the OC4J instances to which the requests were routed and the path for the OC4J Mount directive in the mod_oc4j.conf file.

The following table lists the metrics and their descriptions.

Note:

For target versions 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 30 minutes.

Table 15-6 mod_oc4j MountPt Metrics

Metric	Description
Failover.count, ops	Total number of failovers for this mount point
OC4J Instance Name(s)	OC4J Instance(s) to which the requests were routed
Percentage of Requests that Were Failures	Section 15.4.1, "Percentage of Requests that Were Failures"
Percentage of Requests that Were Session Requests	Percentage of total number of requests for this particular mount point routed by mod_oc4j that were session requests, during the last collection interval
Requests Per Second Routed to this Mount Point	Number of requests routed per second by mod_oc4j for this particular mount point
Total Failed Requests to Mount Point	Total number of failed requests routed by mod_oc4j for this particular Mount Point
Total Successful Requests to Mount Point	Total number of successful requests routed by mod_oc4j for this particular Mount Point

15.4.1 Percentage of Requests that Were Failures

The percentage of total number of requests routed by mod_oc4j for this particular mount point that were failed requests.

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 15-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
9.0.4.x and 10.1.2.x	Every 30 Minutes	After Every Sample	>	1	1.5	2	The percentage of requests that resulted in failures is %value%%%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Mount Point" object.

If warning or critical threshold values are currently set for any "Mount Point" 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 "Mount Point" object, use the Edit Thresholds page.

15.5 mod_oc4j Request Failure Causes Metrics

This metric category provides graph data for Internal server errors. These errors could have several causes, including: mod_oc4j's inability to initialize internal data structures, unavailability of the Java Virtual Machine (JVM), network errors, and configuration errors.

The following table lists the metrics.

Note:

For target versions 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 5 minutes.

Table 15-8 ,mod_oc4j Request Failure Causes Metrics

Metric
Host
iasInstance
IncorrectReqInit.count, ops
Internal Errors Per Second - Rate at which an internal error occurred while routing requests
modoc4j
Name
Oc4jUnavailable.count, ops
Process
timeStamp.ts, milliseconds
uid
UnableToHandleReq.count, ops

15.6 modplsql_Cache Metrics

Status information for the session cache and content cache.

The Session cache is Portal Application specific:

OracleAS Portal uses session cookies to maintain session details for each OracleAS Portal user. The session cookie is encrypted and contains important information, including: the database username, the lightweight username, and the Globalization Support characteristics of the session. In order for mod_plsql to execute a OracleAS Portal request, it needs to get hold of the database username from the session cookie. To avoid performing an expensive decrypt operation with each user request, mod_plsql decrypts the session cookie once and maintains the relevant details in a OracleAS Portal session cache that is stored on the local file system.

The Content Cache is used by any mod_plsql application which has specified its content to be cacheable.

The following table lists the metric, description, and user action where available.

Note:

For target versions 9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 5 minutes.

Table 15-9 modplsql_Cache Metrics

Metric	Description	User Action
cacheStatus.value	Indicates the status of each cache. Either Up or Down.	Typically this value will be Up. If down verify whether caching is enabled in the mod_plsql cache configuration. If enabled and down verify that the directory in the cache configuration exists and has the correct read/write permissions for the user running this OracleAS.
hits.count, ops	Number of requests that resulted in a cache hit	Actions based on this are dependent on the application, the number of distinct users and cacheability of content.
hits.percentage	Percentage of requests that resulted in a cache hit	Actions based on this are dependent on the application, the number of distinct users and cacheability of content.
modplsql	modplsql	Not Applicable
Name	Name	Not Applicable
newMisses.count, opt	Number of requests that resulted in a cache miss, where the requested content was not in the cache at all.	Actions based on this are dependent on the application, the number of distinct users and cacheability of content.
newMisses.percentage	Percentage of requests that resulted in a cache miss, where the requested content was not in the cache at all.	Actions based on this are dependent on the application, the number of distinct users and cacheability of content.
requests.count	Number of requests each cache has serviced since startup	The volume of requests here will be dependent on the usage of the site and volume of calls to cacheable mod_plsql content and number of distinct user sessions. High or low values here need to be correlated to the usage of the application, the number of distinct users and cacheability of content
staleMisses.count, ops	Number of requests that resulted in a cache miss, where the requested content was in the cache but was stale.	Actions based on this are dependent on the application and number of distinct users and cacheability of content.
staleMisses.percentage	Percentage of requests that resulted in a cache miss, where the requested content was in the cache but was stale	Actions based on this are dependent on the application and number of distinct users and cacheability of content

15.7 modplsql_HTTPResponseCodes Metrics

This metric category provides information about the count or percentage of various types of response codes since the Application Server was last restarted.

The following table lists the metric, description, and user action where available.

Note:

For target versions 9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 5 minutes.

Table 15-10 modplsql_HTTPResponseCodesMetrics

Metric	Description	User Action
HTTP 200s	Count of successful mod_plsql requests returning a 200 HTTP response code	The value indicates successful responses. Customers should not take any action based on the value for this metric.
HTTP 200s percentage	Percentage of successful mod_plsql requests returning a 200 HTTP response code.	The value indicates the percentage of successful responses. Customers should not take any action based on the value for the metric.
HTTP 300s Resolved	Count of successful mod_plsql requests returning a 300 HTTP response code.	The value indicates successful responses. Customers should not take any action based on the value for this metric.
HTTP 300s resolved percentage	Percentage of successful mod_plsql requests returning a 300 HTTP response code.	The value indicates the percentage of successful responses. Customers should not take any action based on the value for the metric.
HTTP 400s	Count of unsuccessful mod_plsql requests returning a 400 HTTP response code.	If there is a high volume of failures, the Apache error logs should be examined to determine which requests are failing. For example, a DAD could be misconfigured, or the Database housing a specific mod_plsql DAD could be unavailable.
HTTP 400s percentage	See Section 15.7.1, "HTTP 400s percentage"	See Section 15.7.1, "HTTP 400s percentage"
HTTP 500s	Count of unsuccessful mod_plsql requests returning a 500 HTTP response code.	If there is a high volume of failures, the Apache error logs should be examined to determine which requests are failing. For example, a DAD could be misconfigured, or the Database housing a specific mod_plsql DAD could be unavailable.
HTTP 500s percentage	See Section 15.7.2, "HTTP 500s percentage"	Section 15.7.2, "HTTP 500s percentage"
Total HTTP responses	Count of mod_plsql requests	Customers should not take any action based on the value of this metric.

15.7.1 HTTP 400s percentage

Percentage of unsuccessful mod_plsql requests returning a 400 HTTP response code.

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 15-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
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	Not Defined	Not Defined	2	HTTP 400 response codes are %value% %

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Full Name" object.

If warning or critical threshold values are currently set for any "Full 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 "Full Name" object, use the Edit Thresholds page.

User Action

If there is a high percentage of failures, the Apache error logs should be examined to determine which requests are failing. For example, a DAD could be misconfigured, or the Database housing a specific mod_plsql DAD could be unavailable.

15.7.2 HTTP 500s percentage

Percentage of unsuccessful mod_plsql requests returning a 500 HTTP response code.

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 15-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
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	Not Defined	Not Defined	2	HTTP 500 response codes are %value% %

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Full Name" object.

If warning or critical threshold values are currently set for any "Full 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 "Full Name" object, use the Edit Thresholds page.

User Action

If there is a high percentage of failures, the Apache error logs should be examined to determine which requests are failing. For example, a DAD could be misconfigured, or the Database housing a specific mod_plsql DAD could be unavailable.

15.8 modplsql_RequestGroupingSQLErrorList Metrics

The following table lists the metrics.

Note:

For target versions 9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 5 minutes.

Table 15-13 modplsql_RequestGroupingSQLErrorList Metrics

Metric
errorCount.count
lastErrorDate.value
LastErrorRequest.value
LastErrorText.value
Name

15.9 modplsql_RequestLast10SQLErrorList Metrics

This category of metrics provides information about PL/SQL exception stacks.

Note:

For target versions9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 5 minutes.

Table 15-14 modplsql_RequestLast10SQLErrorList Metrics

Metric
errorDate.value
errorRequest.value
errorText.value
Name

15.10 OHS Child Process Metrics

This metric category contains metrics about Oracle HTTP Server child processes. The following table lists the metrics and their descriptions.

Table 15-15 OHS Child Process Metrics

Metric	Description
Process ID	PID of the process servicing a request
Processing Time (msecs)	Time spent processing the request
Processing Time (usecs)	Time spent processing the request
Slot ID	Position of the process in Oracle HTTP Server's internal data structures
Status	The state of processing. Can be: keepalive: The server is servicing a keepalive (persistent HTTP) request. dead: The server is down. starting: The server is spawning. ready: The server is ready and waiting for a connection. reading: The server is reading data from a client (browser). writing: The server is writing data to a client (browser). logging: The server is writing to a log file. dns_wait: The server is performing a DNS lookup. finishing: The server is performing a graceful restart (without dropping all pending connects).
url.value	URL being processed

15.11 OHS General Metrics

This metric category includes metrics that provide general information about Oracle HTTP Server.

Note:

For target versions 9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 5 minutes.

15.11.1 Start Time (ms since Epoch)

This metric contains the start time of the HTTP Server. It is represented in milliseconds since the Unix epoch.

The UNIX epoch is January 1, 1970.

15.12 OHS Module Metrics

Contains metrics about Oracle HTTP Server (OHS) modules. The following table lists the metrics and their descriptions.

Note:

For all target versions, the collection frequency for each metric is every 5 minutes.

Table 15-16 OHS Module Metrics

Metric	Description
Active Requests for a Module	The number of requests currently being processed by this module's handler
Request Handling Throughput, for a Module (requests per second)	This rate metric tells you the number of requests handled per second by this module during the last interval. The interval is the period of time specified as the collection frequency for this metric. This metric helps you determine the frequency of requests currently being served by the module. If the request handling throughput is very low, either there is no activity on the Web server for the module, or there is something else going on that is preventing the module from processing requests.
Request Handling Time, for a Module (seconds)	Average time (in seconds) it took the module to handle a request during the last interval. The interval is the period of time specified as the collection frequency for this metric.

Metric

Description

Active Requests for a Module

The number of requests currently being processed by this module's handler

Request Handling Throughput, for a Module (requests per second)

This rate metric tells you the number of requests handled per second by this module during the last interval. The interval is the period of time specified as the collection frequency for this metric.

This metric helps you determine the frequency of requests currently being served by the module. If the request handling throughput is very low, either there is no activity on the Web server for the module, or there is something else going on that is preventing the module from processing requests.

Request Handling Time, for a Module (seconds)

Average time (in seconds) it took the module to handle a request during the last interval. The interval is the period of time specified as the collection frequency for this metric.

15.13 OHS Process Metrics

This metric category contains metrics about DMS processes.

15.13.1 Heap Usage (MB)

Displays (in MB) the total amount of heap space used since the server 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 15-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
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	Not Defined	Not Defined	2	Heap Usage is %value%MB

15.14 OHS Response Code Metrics

This metric category includes metrics about the count of Oracle HTTP Server response codes since the Application Server was last restarted. The following table lists the metrics.

Note:

For target versions 9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 15 minutes.

Table 15-18 OHS Response Code Metrics

Metric
HTTP 4xx errors
HTTP 5xx errors

15.15 OHS Server Metrics

The metrics in this metric category display information about Oracle HTTP Server.

Note:

For target versions 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 30 minutes.

15.15.1 Active HTTP Connections

This metric shows the number of open HTTP connections.

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 15-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	>	7500	8000	2	The number of active connections is %value%

15.15.2 Active HTTP Requests

The number of requests currently being serviced.

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 15-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	>	7500	8000	2	The number of active requests is %value%

15.15.3 Busy Processes

The number of child servers that are busy.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes

15.15.4 Connection Duration (seconds)

This metric shows the average time (in seconds) a connection was open during the last interval. The interval is the period of time specified as the collection frequency for this metric. A connection remains open until all of the requests that it is handling have been completed.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 5 Minutes

15.15.5 Error Rate (%)

The percentage of requests that encountered errors during the last 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 15-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
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	1	1.5	2	The percentage of requests that resulted in errors is %value%%%

User Action

Use the Enterprise Manager Application Server Control Console to examine the errors in this HTTP Server's error log file. For information about viewing HTTP Server error logs in the Enterprise Manager Application Server Control, see the "About the HTTP Server Log Files" topic in the Enterprise Manager Application Server Control help system.

15.15.6 Idle Processes

The number of child servers that are ready.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes

15.15.7 Percentage of Busy Processes

Shows the percentage of Oracle HTTP Server child processes that are currently servicing requests.

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 15-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
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	85	90	2	The percentage of processes that are busy handling requests is %value%%%

User Action

To tune the percentage of Oracle HTTP Server child processes that are currently servicing requests, you can change the values for the MaxClients, MinSpareServers, and MaxSpareServers directives.

You can change the value of the MaxClients directive by modifying the value of the Maximum Requests Processed Simultaneously field on the HTTP Server Server Properties page in the Enterprise Manager Application Server Control Console. See the "Modifying Server Properties" topic in the Enterprise Manager Application Server Control help system for more information about accessing the HTTP Server Server Properties page in the Enterprise Manager Application Server Control Console. Click Help on the HTTP Server Server Properties page for more information about using that page.

The MinSpareServers and MaxSpareServers directives can be modified on the Advanced Server Properties page in the Enterprise Manager Application Server Control Console. See the "Editing the Server Configuration Files" topic in the Enterprise Manager Application Server Control help system for more information about accessing the HTTP Server Advanced Server Properties page in the Enterprise Manager Application Server Control Console. Click Help on the HTTP Server Advanced Server Properties page for more information about using that page to edit the directives in the httpd.conf file.

For more information about the MaxClients, MinSpareServers, and MaxSpareServers directives, go to the Apache HTTP Server Documentation section of the http://www.apache.org Web site, then navigate to the Directives information.

15.15.8 Request Processing Time (seconds)

This metric shows the average time it took to process a request during the last 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 15-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 average processing time for a request is %value% seconds

15.15.9 Request Throughput (requests per second)

This rate metric tells you the number of requests per second serviced during the last interval. The interval is the period of time specified as the collection frequency for this metric.

This metric tells you how much of a load this HTTP Server is handling.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 5 Minutes

15.15.10 Response Data Processed (KB per response)

This metric tells you the average size of a response (in KB) during the last 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 15-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
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	Not Defined	Not Defined	2	The average size of a request is %value%KB

15.15.11 Response Data Throughput (KB per second)

This metric tells you the amount of response data (in KB/seconds) processed by Oracle HTTP Server during the last 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.

Target Version	Collection Frequency
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes

User Action

This metric can help you identify changes in the volume of information being served by the HTTP Server over time.

15.16 OHS Virtual Host Metrics

The metrics in this metric category provide virtual host information.

Note:

For target versions 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 30 minutes.

15.16.1 Active Requests for a Virtual Host

Total number of active requests currently being processed by the virtual host.

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 15-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
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	7500	8000	2	The number of active requests for virtual host %name% is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Name" object.

If warning or critical threshold values are currently set for any "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 "Name" object, use the Edit Thresholds page.

15.16.2 Request Processing Time for a Virtual Host (seconds)

This metric shows the average amount of time it took the virtual host to process one request during the last 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 15-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
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	Not Defined	Not Defined	2	The average processing time for a request for virtual host %name% is %value% seconds

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Name" object.

If warning or critical threshold values are currently set for any "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 "Name" object, use the Edit Thresholds page.

15.16.3 Request Throughput for a Virtual Host (requests per second)

This rate metric tells you the number of requests per second serviced by the virtual host during the last interval. The interval is the period of time specified as the collection frequency for this metric.

This metric tells you how much of a load this virtual host is handling.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes

15.16.4 Response Data Processed for a Virtual Host (KB per response)

This metric tells you the average size of a response (in KB) during the last 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 15-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
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	Not Defined	Not Defined	2	The average size of a request for virtual host %name% is %value%KB

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Name" object.

If warning or critical threshold values are currently set for any "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 "Name" object, use the Edit Thresholds page.

15.16.5 Response Data Throughput for a Virtual Host (KB per second)

This metric tells you the amount of response data (in KB/second) processed by the virtual host during the last 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.

Target Version	Collection Frequency
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes

User Action

This metric can help you identify changes in the volume of information being served by the virtual host over time.

15.16.6 Virtual Host Type

The type of virtual host, either IP_DEFAULT, NAME_DEFAULT, IP_BASED, or NAME_BASED.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
9.0.4.x and 10.1.2.x	Every 5 Minutes

15.17 Process Metrics

Metrics for processes. The following table lists the metrics and their descriptions.

Table 15-28 Process Metrics

Metric	Description
Host	Name of the host on which the process is running
Name	Process name

15.18 Resource Usage

The metrics in this metric category provide information about CPU and memory usage. The following table lists the metrics and their descriptions.

Note:

For target versions 9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 5 minutes.

Table 15-29 Resource Usage Metrics

Metric	Description
CPU Idle Time (%)	Displays the percentage of system CPU time that is idle
CPU Usage (%)	See Section 15.18.1, "CPU Usage (%)"
Free Memory (%)	Shows the percentage of free physical memory for the system
Free Memory (MB)	Shows the amount of free physical memory (ion MB) for the system
Memory Usage (%)	See Section 15.18.2, "Memory Usage (%)"
Memory Usage (MB)	Shows the amount of physical memory (in MB) being used by Oracle HTTP Server
Other CPU Usage (%)	See Section 15.18.3, "Other CPU Usage (%)"
Other Memory Usage (%)	See Section 15.18.4, "Other Memory Usage (%)"
Other Memory Usage (MB)	See Section 15.18.5, "Other Memory Usage (MB)"
Start Time (ms since Epoch)	Start time of the HTTP Server. It is represented in milliseconds since the UNIX epoch. For target versions 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 5 minute The UNIX epoch is January 1, 1970.
Total Memory (MB)	Amount of physical memory (in MB) for the system

15.18.1 CPU Usage (%)

Shows the percentage of the CPU usage by Oracle HTTP Server.

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 15-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
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	Not Defined	Not Defined	2	CPU Utilization is %value%%%

15.18.2 Memory Usage (%)

Shows the percentage of the physical memory used by Oracle HTTP Server.

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 15-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
9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x	Every 5 Minutes	After Every 12 Samples	>	80	90	2	Memory Utilization is %value%%%

15.18.3 Other CPU Usage (%)

Shows the percentage of the CPU owned and used by host processes other than Oracle HTTP Server. If you are having problems with CPU usage on the HTTP Server host computer, this metric can help you determine whether or not HTTP Server is causing the problem.

User Action

Navigate to the host Home page in the Application Server Control and review the top processes to see if you can identify which processes are consuming the most CPU. Or, navigate to the host Performance page in the Grid Control and view the processes that are consuming the most CPU.

15.18.4 Other Memory Usage (%)

This metric shows the percentage of host memory in use by processes and applications other than Oracle HTTP Server. If you are having problems with memory usage on the HTTP Server host computer, this metric can help you determine whether or not the HTTP Server is causing the problem.

User Action

Navigate to the host Home page in the Application Server Control and review the top processes to see if you can identify which processes are consuming the most memory. Or, navigate to the host Performance page in the Grid Control and view the processes that are consuming the most memory.

15.18.5 Other Memory Usage (MB)

Shows the physical memory usage (in MB) by processes and applications other than Oracle HTTP Server. If you are having problems with memory usage on the HTTP Server host computer, this metric can help you determine whether or not HTTP Server is causing the problem.

User Action

Navigate to the host Home page in the Application Server Control and review the top processes to see if you can identify which processes are consuming the most memory. Or, navigate to the host Performance page in the Grid Control and view the processes that are consuming the most memory.

15.18.6 Start Time (ms since Epoch)

This metric contains the start time of the HTTP Server. It is represented in milliseconds since the Unix epoch.

The Unix epoch is January 1, 1970.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
9.0.4.x and 10.1.2.x	Every 5 Minutes

15.19 Response

Contains metrics that provide basic information about the HTTP Server.

Note:

For target versions 9.0.4.x and 10.1.2.x, the collection frequency for each metric is every 30 minutes.

15.19.1 UpDown Status

Shows whether the HTTP Server is up or 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 15-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 Minute	After Every 60 Samples	=	Not Defined	0	1	The HTTP Server instance is down

User Action

If the HTTP Server is down, start it using the Home page for the HTTP Server in the Enterprise Manager Application Server Control.