| 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 |
You can use Oracle Enterprise Manager to view the overall status of OracleAS Web Cache. You can also use Enterprise Manager to view OracleAS Web Cache performance metrics that have been collected by the Oracle Agent.
This metric serves as a container for the Cache Performance metrics.
The percentage of the maximum cache size that is allocated to cached objects. The maximum cache size is configured in the Resource Limits and Timeouts page of (Web Cache Home page > Administration tab > Web Cache> Resource Limits link).
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 22-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 |
> |
90 |
99 |
2 |
The cache is using %value%%% of its allocated memory |
By default, this metric has a critical threshold of 99 and a warning threshold of 90. A critical alert is generated when the metric value exceeds the critical threshold value 2 times. A warning alert is generated when the metric value exceeds the warning threshold value 2 times. You can edit the value for a threshold as required.
By default, Enterprise Manager tests the value of this metric every 24 hours.
When an alert is generated, the alert text is:
The cache is using %value%%% of its allocated memory
User Action
When the cache size reaches 90 percent, the cache will start forced garbage collection.
The percentage of requests for content which is cacheable but was not available in the cache.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
Check caching rules configuration from the Rules page (Web Cache Home page > Administration tab > Properties > Application > Rules).
The number of objects stored in the cache, plus the number of objects in transit through the cache. The number includes objects that have expired or have been invalidated but which have not been deleted from the cache. For a cache cluster member, this number represents owned content.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
No user action necessary. This metric is intended for informational purposes only.
The number of bytes that are saved due to in-cache compression as a percentage of the total number of bytes, before compression, in the objects served.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
No user action necessary. This metric is intended for informational purposes only.
The average number of megabytes served by the cache per second during the current time period.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the number of hits is low, then perform the following:
Review the caching rules configuration in the Rules page (Web Cache Home page > Administration tab > Properties > Application > Rules).
In the Popular Requests page (Web Cache Home page > Performance tab > All Sites section > Popular Requests link), select Not Cached from the View list to view the most frequent misses, and then click Go to see the results.
In the results table, view the Reason column for the most frequent URL requests that were not cached.
The percentage of requests that resulted in the cache serving error pages.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
Refer to the specific error being served.
The average number of requests served by cache content per second during the current time period.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the number of hits is low, then perform the following:
Review the caching rules configuration in the Rules page (Web Cache Home page > Administration tab > Properties > Application > Rules).
In the Popular Requests page (Web Cache Home page > Performance tab > All Sites section > Popular Requests link), select Not Cached from the View list to view the most frequent misses, and then click Go to see the results.
In the results table, view the Reason column for the most frequent URL requests that were not cached.
The percentage of requests resolved by cache content. This percentage should be high, except when objects are being invalidated.
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 22-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 |
< |
30 |
20 |
3 |
%value%%% of requests were cache hits |
By default, this metric has a critical threshold of 20 and a warning threshold of 30. A critical alert is generated when the metric value falls short of the critical threshold value 3 times. A warning alert is generated when the metric value falls short of the warning threshold value 3 times. You can edit the value for a threshold as required.
By default, Enterprise Manager tests the value of this metric every 24 hours.
When an alert is generated, the alert text is:
%value%%% of requests were cache hits
User Action
If the number of hits is low, then perform the following:
Review the caching rules configuration in the Rules page (Web Cache Home page > Administration tab > Properties > Application > Rules).
In the Popular Requests page (Web Cache Home page > Performance tab > All Sites section > Popular Requests link), select Not Cached from the View list to view the most frequent misses, and then click Go to see the results.
In the results table, view the Reason column for the most frequent URL requests that were not cached.
The average number of objects invalidated from the cache per second during the current time period.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
The ratio of invalidated objects to invalidation requests can help you determine invalidation performance. You can determine this ratio in the Invalidations page of Grid Control. To navigate to the Invalidations page:
From the Web Cache Home page, click the Performance tab.
In the Related Links section of the Performance tab, click Invalidations.
Note that if invalidation is frequent, then performance may degrade.
The average number of invalidation requests processed by the cache per second during the current time period.
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 22-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 |
> |
100 |
120 |
2 |
The cache encountered %value% invalidation requests per second |
By default, this metric has a critical threshold of 120 and a warning threshold of 100. A critical alert is generated when the metric value exceeds the critical threshold value 2 times. A warning alert is generated when the metric value exceeds the warning threshold value 2 times. You can edit the value for a threshold as required.
By default, Enterprise Manager tests the value of this metric every 24 hours.
When an alert is generated, the alert text is:
The cache encountered %value% invalidation requests per second
User Action
The ratio of invalidated objects to invalidation requests can help you determine invalidation performance. You can determine this ratio in the Invalidations page of Grid Control. To navigate to the Invalidations page:
From the Web Cache Home page, click the Performance tab.
In the Related Links section of the Performance tab, click Invalidations.
Note that if invalidation is frequent, then performance may degrade.
The average number of requests per second for cacheable and non-cacheable content that were not served by the cache during the current time period.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the number of misses is high, then perform the following:
Review the caching rules configuration in the Rules page (Web Cache Home page > Administration tab > Properties > Application > Rules).
In the Popular Requests page (Web Cache Home page > Performance tab > All Sites section > Popular Requests link), select Not Cached from the View list to view the most frequent misses, and then click Go to see the results.
In the results table, view the Reason column for the most frequent URL requests that were not cached.
The number of error pages that the cache has served per second due to a network error while connecting, sending, or receiving response from origin servers for cache-miss 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 22-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 |
> |
.5 |
1 |
2 |
The cache encountered %value% network errors per second |
By default, this metric has a critical threshold of 1 and a warning threshold of .5. A critical alert is generated when the metric value exceeds the critical threshold value 2 times. A warning alert is generated when the metric value exceeds the warning threshold value 2 times. You can edit the value for a threshold as required.
By default, Enterprise Manager tests the value of this metric every 24 hours.
When an alert is generated, the alert text is:
The cache encountered %value% network errors per second
User Action
If the number of network errors is consistently high, then consider improving the network connection between the cache and origin server.
The percentage of requests for non-cacheable content that was not served by the cache.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the number of hits is low, then perform the following:
Review the caching rules configuration in the Rules page (Web Cache Home page > Administration tab > Properties > Application > Rules).
In the Popular Requests page (Web Cache Home page > Performance tab > All Sites section > Popular Requests link), select Not Cached from the View list to view the most frequent misses, and then click Go to see the results.
In the results table, view the Reason column for the most frequent URL requests that were not cached.
The number of incoming open connections to the OracleAS Web Cache server and outgoing open connections to the origin servers.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the number is close to the origin server connection limit, then set a larger capacity for the origin server from the Origin Servers page (Web Cache Home page > Administration tab > Properties > Application > Origin Servers).
The number of error pages that the cache has served per second due to an HTML fragment retrieval problem for a page that supports partial page caching. This number includes errors returned when an uncaught exception occurs in the cache during ESI parsing or when the default ESI fragment is served. A default ESI fragment is served when OracleAS Web Cache is unable to fetch the src specified in the <esi:include> tag.
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 22-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 |
> |
.5 |
1 |
2 |
The cache encountered %value% partial page errors per second |
By default, this metric has a critical threshold of 1 and a warning threshold of .5. A critical alert is generated when the metric value exceeds the critical threshold value 2 times. A warning alert is generated when the metric value exceeds the warning threshold value 2 times. You can edit the value for a threshold as required.
By default, Enterprise Manager tests the value of this metric every 24 hours.
When an alert is generated, the alert text is:
The cache encountered %value% partial page errors per second
User Action
If the number of partial-page errors is consistently high, then improve the origin server side code that generates the ESI pages to catch exceptions.
The percentage of requests that resulted in the cache refreshing content from the origin servers.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
No user action necessary. This metric is intended for informational purposes only.
The average number of requests served by the cache per second during the current time period.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
No user action necessary. This metric is intended for informational purposes only.
The number of error pages that the cache has served per second when origin server capacity has been reached.
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 22-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 |
> |
.5 |
1 |
2 |
The cache encountered %value% site busy errors per second |
By default, this metric has a critical threshold of 1 and a warning threshold of .5. A critical alert is generated when the metric value exceeds the critical threshold value 2 times. A warning alert is generated when the metric value exceeds the warning threshold value 2 times. You can edit the value for a threshold as required.
By default, Enterprise Manager tests the value of this metric every 24 hours.
When an alert is generated, the alert text is:
The cache encountered %value% site busy errors per second
User Action
If the number of site-busy errors is consistently high, then increase the capacity of the origin servers from the Origin Servers page (Web Cache Home page > Administration tab > Properties > Application > Origin Servers).
The size, in megabytes, of the objects currently stored in the cache. For a cache cluster member, this number is an aggregate of the owned and on-demand objects.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
No user action necessary. This metric is intended for informational purposes only.
The percentage of requests resolved by expired or invalidated content in the cache.
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 22-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 |
> |
70 |
80 |
2 |
%value%%% of hits were stale cache hits |
By default, this metric has a critical threshold of 80 and a warning threshold of 70. A critical alert is generated when the metric value exceeds the critical threshold value 2 times. A warning alert is generated when the metric value exceeds the warning threshold value 2 times. You can edit the value for a threshold as required.
By default, Enterprise Manager tests the value of this metric every 24 hours.
When an alert is generated, the alert text is:
%value%%% of hits were stale cache hits
User Action
If the percentage of stale hits is high, then ensure that expired or invalidated pages are updated from the origin server in a timely fashion. Check the network capacity between the OracleAS Web Cache computer and the origin server.
The total number of error pages that the cache has served per second during the current time period.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
No user action necessary. This metric is intended for informational purposes only.
The time at which the cache was started or restarted.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
No user action necessary. This metric is intended for informational purposes only.
These metric columns provide information about Edge Side Includes (ESI).
The number of error pages that the cache has served per second due to exceptions during Edge Side Includes (ESI) parsing or processing. These error pages are typically the result of ESI syntax errors.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| 10.1.2.x | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the number of exception errors is consistently high, then improve the origin server side code that generates the ESI pages to catch exceptions.
The number of default Edge Side Include (ESI) fragments that the cache has served per second. A default ESI fragment is served when OracleAS Web Cache is unable to fetch the src specified in an <esi:include> tag and the alt attribute, onerror attribute, or the try |attempt |except block are either not present or fail.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| 10.1.2.x | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the number of default ESI fragments is consistently high, then review the ESI code.
These metric columns provide information about CPU and memory usage.
The percentage of system CPU time that is idle.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the load is high, then consider upgrading the cache computer.
The amount of free physical memory, in megabytes, for the system.
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 | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the load is high, then consider upgrading the cache computer.
The amount of free physical memory, in megabytes, for the system.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the load is high, then consider upgrading the cache computer.
The percentage of the CPU usage by applications other than OracleAS Web Cache.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If CPU usage is high, then consider upgrading the cache computer.
The percentage of physical memory used by applications other than OracleAS Web Cache.
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 | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the load is high, then consider upgrading the cache computer.
The physical memory usage, in megabytes, by applications other than OracleAS Web Cache.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the load is high, then consider upgrading the cache computer.
The amount of physical memory, in megabytes, for the system.
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 | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the load is high, then consider upgrading the cache computer.
The percentage of the CPU that is being used for OracleAS Web Cache. As traffic increases, CPU utilization increases.
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 22-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 |
CPU Utilization is %value%%% |
By default, this metric has a critical threshold of NotDefined and a warning threshold of NotDefined. A critical alert is generated when the metric value exceeds the critical threshold value 2 times. A warning alert is generated when the metric value exceeds the warning threshold value 2 times. You can edit the value for a threshold as required.
By default, Enterprise Manager tests the value of this metric every 24 hours.
When an alert is generated, the alert text is:
CPU Utilization is %value%%%
User Action
If the load is high, then consider upgrading the cache computer.
The percentage of the physical memory used by OracleAS Web Cache.
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 22-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 |
> |
80 |
90 |
2 |
Memory Utilization is %value%%% |
By default, this metric has a critical threshold of 90 and a warning threshold of 80. A critical alert is generated when the metric value exceeds the critical threshold value 2 times. A warning alert is generated when the metric value exceeds the warning threshold value 2 times. You can edit the value for a threshold as required.
By default, Enterprise Manager tests the value of this metric every 24 hours.
When an alert is generated, the alert text is:
Memory Utilization is %value%%%
User Action
If the load is high, then consider upgrading the cache computer.
The amount of physical memory, in megabytes, that is being used by OracleAS Web Cache.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
By default, Enterprise Manager tests the value of this metric every 24 hours.
User Action
If the load is high, then consider upgrading the cache computer.
This category indicates whether the OracleAS Web Cache instance is up and running or down and unavailable.
This metric indicates whether the OracleAS Web Cache instance is up and running or down and unavailable.
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 22-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 |
|---|---|---|---|---|---|---|---|
|
10.1.2.x |
Every Minute |
After Every 60 Samples |
= |
Not Defined |
0 |
1 |
The OracleAS Web Cache instance is down |
By default, this metric has a critical threshold of 0. A critical alert is generated when the metric value equals the critical threshold value 1 time. You can edit the value for a threshold as required.
By default, Enterprise Manager tests the value of this metric every 24 hours.
When an alert is generated, the alert text is:
The Oracle Web Cache instance is down
The columns in this metric provide information about the performance of origin server.
The current number of open connections that the cache has open to the origin server per second.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Origin Server Name" and "Port" objects.
If warning or critical threshold values are currently set for any unique combination of "Origin Server Name" and "Port" 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 "Origin Server Name" and "Port" 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.
User Action
If the number is close to the connection limit, then set a larger capacity for the origin server from the Origin Servers page (Web Cache Home page > Administration tab > Properties > Application > Origin Servers).
The host name of the origin server.
User Action
No user action necessary. This metric is intended for informational purposes only.
The port at which the origin server listens for the requests from OracleAS Web Cache
User Action
No user action necessary. This metric is intended for informational purposes only.
The average number of seconds used to process a request during the current time period.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Origin Server Name" and "Port" objects.
If warning or critical threshold values are currently set for any unique combination of "Origin Server Name" and "Port" 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 "Origin Server Name" and "Port" 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.
User Action
If the number is low, then improve the connection between the cache and origin server, or upgrade the origin server computer.
Specifies whether or not the origin server is a proxy server. YES specifies that the origin server is a proxy server. NO specifies that the origin server is an application Web sever.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Origin Server Name" and "Port" objects.
If warning or critical threshold values are currently set for any unique combination of "Origin Server Name" and "Port" 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 "Origin Server Name" and "Port" 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.
User Action
No user action necessary. This metric is intended for informational purposes only.
The average number of requests served per second during the current time period.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Origin Server Name" and "Port" objects.
If warning or critical threshold values are currently set for any unique combination of "Origin Server Name" and "Port" 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 "Origin Server Name" and "Port" 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.
User Action
If this number is high, then increase the capacity of this origin server from the Origin Servers page (Web Cache Home page > Administration tab > Properties > Application > Origin Servers), or load balance the requests among cache cluster members.
The current status of the origin server. An up status specifies that the last communication with the origin server was successful. A down status specifies that the origin server is down. If this is the last origin server in a single or multiple server configuration, OracleAS Web Cache continues to forward requests to the origin server. If this is not the last server, then no new requests will be sent to origin server. However, OracleAS Web Cache will poll the inactive origin server until it is back online.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Origin Server Name" and "Port" objects.
If warning or critical threshold values are currently set for any unique combination of "Origin Server Name" and "Port" 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 "Origin Server Name" and "Port" 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.
User Action
No user action necessary. This metric is intended for informational purposes only.
