Oracle Enterprise Manager Event Test Reference Manual Release 9.0.1 Part Number A89872-02 |
|
The e-Business Tools advanced event tests are provided for lights-out event monitoring and problem detection of the HTTP server.
Aside from the basic up/down event tests provided for all services administered in the Oracle Enterprise Manager console, the e-Business tools provide a library of event tests specific to the HTTP Server. The types of event tests associated with the HTTP Server are:
The HTTP Server UpDown event test checks whether the Apache HTTP server being monitored is running.
The threshold event tests are triggered by user-specified metrics. The full descriptions of the individual event tests follow. The event tests are in alphabetical order.
The following table lists the e-Business event tests. The full descriptions of the individual event tests follow the table. The event tests are in alphabetical order.
The e-Business event tests are listed in alphabetical order.
This event test monitors the number of bytes transferred by the HTTP Server per second. The rate is calculated depending on the frequency of the event. For example, if the event was registered with a frequency of 100 seconds, the event will calculate the rate by dividing the number of bytes served in that period by 100.
None
60 seconds
Check the access logs to determine a cause. If the condition persists, tune the system to handle a larger data output.
This event test monitors the number of requests made to the HTTP Server per second. The rate is calculated depending on the frequency of the event. For example, if the event was registered with a frequency of 100 seconds, the event will calculate the rate by dividing the number of requests in that period by 100.
None
60 seconds
Check the access logs to determine a cause. If the condition persists, tune the system to handle a larger number of requests.
This event test monitors the number of servers that the HTTP Server has spawned to handle the incoming requests. The HTTP Server increases the number of servers when there is a greater number of requests to handle and reduces the number of servers when there are fewer requests. This action maximizes the resource utilization on the system.
Note: On Windows NT, servers represent the number of threads while on UNIX systems a server correlates to a process.
None
60 seconds
Check the access logs to determine a cause. If the condition persists, tune the Web Server to use resources more efficiently or upgrade the hardware.
|
Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|