| 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 monitor and manage OracleAS Portal.
The Database Instance metric provides information about the Oracle Database where the OracleAS Portal schema is running. The following table lists the metrics, descriptions, and data sources.
|
Note: For all target versions, the collection frequency for each metric is every 5 minutes. |
Table 19-1 Database Instance Metrics
| Metric | Description | Data Source |
|---|---|---|
|
Instance Name |
Name of the Oracle Database where the OracleAS Portal schema is running |
Instance name in v$instance table |
|
Start Time |
Time the Oracle Database was last started |
Startup_time in v$instance table |
|
Version |
Version of the Oracle Database being used |
Version in v$instance table |
The Database Portlet metric allows you to analyze the performance of individual database portlets. For more information about database portlets, refer to the Oracle Portal Developer Kit (PDK) page located at http://www.oracle.com/technology/products/ias/portal/pdk.html on the Oracle Technology Network (OTN).
Additional documentation is also available from the Oracle Portal documentation page on OTN located at http://www.oracle.com/technology/products/ias/portal/documentation.html.
The following table lists the metrics and their descriptions.
|
Note: For all target versions, the collection frequency for each metric is every 15 minutes. |
|
Note: For each metric you can set different warning and critical threshold values for each unique combination of "Portlet Name", "Portlet ID", and "Provider Name" objects.If warning or critical threshold values are currently set for any object, those thresholds can be viewed on the Metric Detail page for this metric. To specify or change warning or critical threshold values for an object, use the Edit Thresholds page. |
Table 19-2 Database Portlet Metrics
| Metric | Description |
|---|---|
|
Cache Hits |
Number of times database portlet content has been serviced by the cache |
|
Count of HTTP 200 Response codes |
Number of successful requests, that is, HTTP Response and Error Code: 200. |
|
Count of HTTP 400 Response codes |
Number of incomplete requests, that is, HTTP Response and Error Code: 400. |
|
Count of HTTP 500 Response codes |
Number of unsuccessful server errors, that is, HTTP Response and Error Code: 500. Error Code: 500 typically means something is wrong with the server, check that the server hosting the database portlet is accessible. |
|
Count of requests which timed out |
Number of requests to this database portlet that timed out. |
|
Count of Resolved HTTP 300 Response codes |
Number of successful requests, that is, HTTP Response and Error Code: 300. Note: A portlet that is initially redirected with a 300 response code, may get logged as a 200 response code if it successfully returns content. |
|
Count of Unresolved HTTP 300 Response codes |
Number of unresolved redirects, that is, HTTP Response and Error Code: 300. Of those portlets that returned an HTTP Response Code of 300, this indicates how many redirected requests remain unresolved. For example, an unresolved request gets redirected to another address, that returns an unresolved error code. |
|
Database Portlet Average Time (msec) |
Average time (msec) to request this database portlet. |
|
Database Portlet Maximum Time (msec) |
Maximum time (msec) to request this database portlet. |
|
Database Portlet Minimum Time (msec) |
Minimum time (ms) to request this database portlet. |
|
Last Response Code |
HTTP response code of the last database portlet serviced by the provider. If this response code is not in the 200 or 300 range, there may be an issue with this provider not providing content to the portal. |
|
Requests |
Number of requests made to this database portlet. |
The Database Providers metric allows you to analyze the performance of database providers. For more information about Database Providers, refer to the Oracle Portal Developer Kit (PDK) page located at http://www.oracle.com/technology/products/ias/portal/pdk.html on the Oracle Technology Network (OTN).
Additional documentation is also available from the Oracle Portal documentation page on OTN located at http://www.oracle.com/technology/products/ias/portal/documentation.html. The following table lists the metrics and their descriptions.
|
Note: For all target versions, the collection frequency for each metric is every 15 minutes. |
|
Note: For each metric you can set different warning and critical threshold values for each "Provider Name" object.If warning or critical threshold values are currently set for any "Provider 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 "Provider Name" object, use the Edit Thresholds page. |
Table 19-3 Database Providers Metrics
| Metric | Description |
|---|---|
|
Cache Hits |
Number of times the database providers content has been serviced by the cache. |
|
Count of HTTP 200 Response codes |
Number of successful requests, that is, HTTP Response and Error Code: 200. |
|
Count of HTTP 400 Response codes |
Number of incomplete requests, that is, HTTP Response and Error Code: 400. |
|
Count of HTTP 500 Response codes |
Number of unsuccessful server errors, that is, HTTP Response and Error Code: 500. |
|
Count of requests which timed out |
Number of requests that timed out |
|
Count of Resolved HTTP 300 Response codes |
Number of successful resolved requests, that is, HTTP Response and Error Code: 300. Note: A portlet that is initially redirected with a 300 response code, may get logged as a 200 response code if it successfully returns content. |
|
Count of Unresolved HTTP 300 Response codes |
Number of unresolved redirects, that is, HTTP Response and Error Code: 300. Of those portlets that returned an HTTP Response Code of 300, this indicates how many redirected requests remain unresolved. For example, an unresolved request gets redirected to another address, that returns an unresolved error code. |
|
Database Provider Portlets Average Time (msec) |
Average time (in ms) to request database portlets. Note: There are no multiple thresholds associated with this metric. |
|
Database Provider Portlets Maximum Time (msec) |
See Section 19.3.1, "Database Provider Portlets Maximum Time (msec)" |
|
Database Provider Portlets Minimum Time (msec) |
Minimum time (in ms) to request database portlets |
|
Database Provider Status |
Section 19.3.2, "Database Provider Status" |
|
Offline |
Indicates whether the database provider is currently offline |
|
Percentage of Database Provider HTTP 500 Response codes |
Section 19.3.3, "Percentage of Database Provider HTTP 500 Response codes" |
|
Requests |
Number of requests made to this database portlet |
|
Slowest Average Portlet Time (msec) |
Section 19.3.4, "Slowest Average Portlet Time (msec)" |
The maximum time (in ms) to request database portlets.
By default, this metric has a critical threshold of 10000 and a warning threshold of 6000. A critical alert is generated when the metric value exceeds the critical threshold value. A warning alert is generated when the metric value exceeds the warning threshold value. You can edit the value for a threshold as required.
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 19-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 15 Minutes |
After Every 12 Samples |
> |
6000 |
10000 |
1 |
The maximum portlet response timing for this provider is unacceptable. |
Indicates whether a specific database provider has a problem.
By default, this metric has a critical threshold of DOWN. A critical alert is generated when the metric value equals the critical threshold value. You can edit the value for a threshold as required.
By default, Oracle Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
The last response code from the a portlet serviced by this provider is 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 19-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 15 Minutes |
After Every 12 Samples |
= |
Not Defined |
DOWN |
1 |
The last response code from the a portlet serviced by this provider is down. |
User Action
If the status is 'down', it indicates that at least one of the portlets serviced by this provider's last HTTP response code was unsuccessful. Investigate the provider to determine what is causing the fault.
The percentage of Database Provider requests that returned HTTP 500 response codes, that is, unsuccessful server errors.
By default, this metric has a critical threshold of 15 and a warning threshold of 10. A critical alert is generated when the metric value exceeds the critical threshold value. A warning alert is generated when the metric value exceeds the warning threshold value. You can edit the value for a threshold as required.
By default, Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
The percentage of portlet requests returning unsuccessful is unacceptable for this provider.
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 19-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 15 Minutes |
After Every 12 Samples |
> |
10 |
15 |
1 |
The percentage of portlet requests returning unsuccessful is unacceptable for this provider. |
The average performance of a specific provider's slowest portlet (in ms).
By default, this metric has a critical threshold of 4500 and a warning threshold of 4000. A critical alert is generated when the metric value exceeds the critical threshold value. A warning alert is generated when the metric value exceeds the warning threshold value. You can edit the value for a threshold as required.
By default, Oracle Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
The slowest average portlet response timing for this provider is unacceptable.
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 19-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 15 Minutes |
After Every 12 Samples |
> |
4000 |
4500 |
1 |
The slowest average portlet response timing for this provider is unacceptable. |
The General Page Engine metric allows you to analyze the performance of your portal's Parallel Page Engine. The following table lists the metrics and their descriptions.
|
Note: For all target versions, the collection frequency for each metric is every 10 minutes. |
Table 19-8 General Page Engine Metrics
| Metric | Description |
|---|---|
|
Average Queue Length |
Average number of requests in the Parallel Page Engine internal portal content request queue, since middle tier startup |
|
Average Time in Page Engine Queue (msec) |
Average time (in ms) content requests have spent in the Parallel Page Engines internal request queue. |
|
Cache Hits |
Number of requests for fully cached pages that resulted in content being returned from the cache since middle tier startup. |
|
Percentage of Requests that were serviced by the cache |
Percentage of requests for cacheable, fully assembled pages that resulted in a cache hit. |
|
Percentage of Requests Timing Out in the Page Engine Queue |
See Section 19.4.1, "Percentage of Requests Timing Out in the Page Engine Queue" |
|
Requests for cache enabled pages |
Number of requests for ached enabled pages since middle tier startup |
|
Requests to the Cache |
Number of requests for cacheable, full assembled pages since middle tier startup |
|
Total Page Requests |
Total number of requests for OracleAS Portal pages since middle tier startup |
The percentage of OracleAS Portal content requests that have timed out in the Parallel Page Engine's internal request queue.
By default, this metric has a critical threshold of 15 and a warning threshold of 10. A critical alert is generated when the metric value exceeds the critical threshold value. A warning alert is generated when the metric value exceeds the warning threshold value. You can edit the value for a threshold as required.
By default, Oracle Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
The percentage of requests that have timed out in the internal request queue is unacceptable.
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 19-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 10 Minutes |
After Every 12 Samples |
> |
10 |
15 |
1 |
The percentage of requests that have timed out in the internal request queue is unacceptable. |
The Page Engine Response Code metrics provide HTTP response code information. The following table lists the metrics and their descriptions.
|
Note: For all target versions, the collection frequency for each metric is every 10 minutes. |
Table 19-10 Page Engine Response Code Metrics
| Metric | Description |
|---|---|
|
Percentage of http 200 responses |
Percentage of portlets returning a 200 HTTP Response code - Successful Request. |
|
Percentage of http 300 Resolved responses |
Percentage of portlets returning a 300 HTTP Response code that were resolved. Of those portlets that returned an HTTP Response Code of 300, how many were redirected resolved. |
|
Percentage of http 300 Unresolved responses |
Percentage of portlets returning a 300 HTTP Response code that were unresolved. Of those portlets that returned an HTTP Response Code of 300, this indicates how many redirected requests remain unresolved. For example, an unresolved request gets redirected to another address, that returns an unresolved error code |
|
Percentage of http 400 responses |
Percentage of portlets returning a 400 HTTP Response code - Unsuccessful Request Incomplete. |
|
Percentage of http 500 responses |
Percentage of portlets returning a 500 HTTP Response code - Unsuccessful Server Errors. |
|
Timeouts |
Number of timeouts registered by the Parallel Page Engine. |
|
Total http 200 responses |
Number of successful requests to portlets, that is, HTTP Response and Error Code: 200. |
|
Total http 300 Resolved responses |
Number of successful resolved requests to portlets, that is, HTTP Response and Error Code: 300. Note: A portlet that is initially redirected with a 300 response code, may get logged as a 200 response code if it successfully returns content. |
|
Total http 300 Unresolved responses |
Number of unresolved redirects from portlet requests, that is, HTTP Response and Error Code: 300. Of those portlets that returned an HTTP Response Code of 300, this indicates how many redirected requests remain unresolved. For example, an unresolved request gets redirected to another address, that returns an unresolved error code. |
|
Total http 400 responses |
Number of incomplete requests to portlets, that is, HTTP Response and Error Code: 400. |
|
Total http 500 responses |
Number of unsuccessful server errors, that is, HTTP Response and Error Code: 500. |
|
Total requests |
Total number of portlets requested by the Parallel Page Engine. |
|
Unresolved Redirects |
Number of Unresolved Redirects registered by the Parallel Page Engine. |
The response of a request to the OracleAS Portal default home page.
The time (in ms) to download the OracleAS Portal home page.
By default, this metric has a critical threshold of 3000 and a warning threshold of 2000. A critical alert is generated when the metric value exceeds the critical threshold value. A warning alert is generated when the metric value exceeds the warning threshold value. You can edit the value for a threshold as required.
By default, Oracle Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
The Portal Instance homepage performance is unacceptable.
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 19-11 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every 12 Samples |
> |
2000 |
3000 |
1 |
The Portal Instance homepage performance is unacceptable. |
Indicates whether or not the OracleAS Portal home page has been called successfully. The status value '1' indicates success.
By default, this metric has a critical threshold of 0. A critical alert is generated when the metric value equals the critical threshold value. You can edit the value for a threshold as required.
By default, Oracle Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
The Portal instance is not accessible.
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 19-12 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every 12 Samples |
= |
Not Defined |
0 |
1 |
The Portal instance is not accessible. |
The Portal Metadata Repository Version Metric indicates the version of OracleAS Portal that is currently running.
The response of two requests to test the status of OracleAS Portal.
Indicates whether or not OracleAS Portal is functioning.
The status is based on the success of two URL calls, one to a test package via mod_plsql and the other to the Parallel Page Engine (PPE):
mod_plsql ping to: <protocol>://<host>:<port>/pls/<DAD>/htp.p?cbuf=Test
PPE ping to: <protocol>://<host>:<port>/portal/page
By default, this metric has a critical threshold of 0. A critical alert is generated when the metric value equals the critical threshold value. You can edit the value for a threshold as required.
By default, Oracle Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
The Portal instance is not accessible.
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 19-13 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every 12 Samples |
= |
Not Defined |
0 |
1 |
The Portal instance is not accessible. |
The Syndication Server Status Metric provides status information for the Syndication Server.
The Top Level Monitoring Status Metric indicates whether or not the services required by OracleAS Portal to monitor the portal instance are up and running.
Indicates whether or not the services required by OracleAS Portal to adequately monitor the portal instance are running. The status value '1' indicates the services are running OK.
The test involves an HTTP ping check on the monitoring witness servlet. This also tests the DMS servlet and therefore, the ability to obtain OracleAS Portal DMS based metrics, such as the Provider, Portlet and Parallel Page Engine metrics.
By default, a critical or warning threshold value (or both) is set for this metric column. Alerts are generated when threshold values are reached. You can edit these threshold values, if required.
For all target versions, the collection frequency for this metric is every 10 minutes.
The Ultra Search Status Metric provides status information for Oracle Ultra Search.
If the status value is '1', users can login to the Ultra Search administration tool via SSO in an Oracle Internet Directory (OID) enabled database tier environment.
By default, this metric has a critical threshold of 0. A critical alert is generated when the metric value equals the critical threshold value. You can edit the value for a threshold as required.
By default, Oracle Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
Ultra Search is not accessible.
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 19-14 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 10 Minutes |
After Every 12 Samples |
= |
Not Defined |
0 |
1 |
Ultra Search is not accessible. |
The Web Portlet Metric allows you to analyze the performance of individual Web provider portlets. For more information about Web providers, refer to the Oracle Portal Developer Kit (PDK) page located at http://www.oracle.com/technology/products/ias/portal/pdk.html on the Oracle Technology Network (OTN).
Additional documentation is also available from the Oracle Portal documentation page on OTN located at http://www.oracle.com/technology/products/ias/portal/documentation.html.
The following table lists the metrics and their descriptions.
|
Note: For all target versions, the collection frequency for each metric is every 15 minutes. |
|
Note: For each metric you can set different warning and critical threshold values for each unique combination of "Portlet Name", "Portlet ID", and "Provider Name" objects.If warning or critical threshold values are currently set for any object, those thresholds can be viewed on the Metric Detail page for this metric. To specify or change warning or critical threshold values for an object, use the Edit Thresholds page. |
Table 19-15 Web Portlet Metrics
| Metric | Description |
|---|---|
|
Cache Hits |
Number of times the portlet's content has been serviced by the cache |
|
Count of HTTP 200 Response codes |
Number of successful requests, that is, HTTP Response and Error Code: 200. |
|
Count of HTTP 400 Response codes |
Number of incomplete requests, that is, HTTP Response and Error Code: 400. |
|
Count of HTTP 500 Response codes |
Number of unsuccessful server errors, that is, HTTP Response and Error Code: 500. |
|
Count of requests which timed out |
Number of requests that timed out |
|
Count of Resolved HTTP 300 Response codes |
Number of successful requests, that is, HTTP Response and Error Code: 300. Note: A portlet that is initially redirected with a 300 response code, may get logged as a 200 response code if it successfully returns content. |
|
Count of Unresolved HTTP 300 Response codes |
Number of unresolved redirects, that is, HTTP Response and Error Code: 300. Of those portlets that returned an HTTP Response Code of 300, this indicates how many redirected requests remain unresolved. For example, an unresolved request gets redirected to another address, that returns an unresolved error code. |
|
Last Response Code |
The HTTP response code of the last portlet serviced by the provider. If this response code is not in the 200 or 300 range, this provider may not be providing content to OracleAS Portal. Administrators can use the Portal Developer Kit (PDK) Java test page to check that the machine hosting the provider is accessible and the specific Provider on that machine is working. |
|
Requests |
Number of requests made to this Web portlet |
|
Web Portlet Average Time (msec) |
Average time (in ms) to request this Web portlet |
|
Web Portlet Maximum Time (msec) |
Maximum time (in ms) to request this Web portlet |
|
Web Portlet Minimum Time (msec) |
Minimum time (in msec) to request this Web portlet |
The Web Providers metric allows you to analyze the performance of Web providers.
For more information about Web providers, refer to the Oracle Portal Developer Kit (PDK) page located at http://www.oracle.com/technology/products/ias/portal/pdk.html on the Oracle Technology Network (OTN).
Additional documentation is also available from the Oracle Portal documentation page on OTN located at http://www.oracle.com/technology/products/ias/portal/documentation.html.
|
Note: For all target versions, the collection frequency for each metric is every 15 minutes. |
|
Note: For each metric you can set different warning and critical threshold values for each "Provider Name" object.If warning or critical threshold values are currently set for any "Provider 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 "Provider Name" object, use the Edit Thresholds page. |
Table 19-16 Web Providers Metrics
| Metric | Description |
|---|---|
|
Cache Hits |
Number of times the Provider's content has been serviced by the cache. |
|
Count of HTTP 200 Response codes |
Number of successful requests to portlets, that is, HTTP Response and Error Code: 200. |
|
Count of HTTP 400 Response codes |
Number of portlets returning a 400 HTTP Response code - Unsuccessful Request Incomplete. |
|
Count of HTTP 500 Response codes |
Number of unsuccessful server errors, that is, HTTP Response and Error Code: 500. |
|
Count of requests which timed out |
Number of requests that timed out |
|
Count of Resolved HTTP 300 Response codes |
Number of successful requests, that is, HTTP Response and Error Code: 300. Note: A portlet that is initially redirected with a 300 response code, may get logged as a 200 response code if it successfully returns content. |
|
Count of Unresolved HTTP 300 Response codes |
Number of unresolved redirects, that is, HTTP Response and Error Code: 300. Of those portlets that returned an HTTP Response Code of 300, this indicates how many redirected requests remain unresolved. For example, an unresolved request gets redirected to another address, that returns an unresolved error code. |
|
Offline |
Indicates if a Web provider is currently offline |
|
Percentage of Web Provider HTTP 500 Response codes |
See Section 19.13.1, "Percentage of Web Provider HTTP 500 Response codes" |
|
Requests |
Number of requests serviced by this Web provider |
|
Slowest Average Portlet Time (msec) |
|
|
Web Provider Portlets Average Time (msec) |
Average time (in ms) to request Web provider portlets |
|
Web Provider Portlets Maximum Time (msec) |
See Section 19.13.3, "Web Provider Portlets Maximum Time (msec)" |
|
Web Provider Portlets Minimum Time (msec) |
Minimum time (in ms) to request Web provider portlets |
|
Web Provider Status |
The percentage of Web Provider requests that returned HTTP 500 response codes, that is, unsuccessful server errors.
By default, this metric has a critical threshold of 15 and a warning threshold of 10. A critical alert is generated when the metric value exceeds the critical threshold value. A warning alert is generated when the metric value exceeds the warning threshold value. You can edit the value for a threshold as required.
By default, Oracle Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
The percentage of portlet requests returning unsuccessful is unacceptable for this provider.
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 19-17 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 15 Minutes |
After Every 12 Samples |
> |
10 |
15 |
1 |
The percentage of portlet requests returning unsuccessful is unacceptable for this provider. |
The average performance of a specific provider's slowest portlet (in ms).
By default, this metric has a critical threshold of 4500 and a warning threshold of 4000. A critical alert is generated when the metric value exceeds the critical threshold value 1 time. A warning alert is generated when the metric value exceeds the warning threshold value. You can edit the value for a threshold as required.
When an alert is generated, the alert text is:
The last response code from the a portlet serviced by this provider is 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 19-18 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 15 Minutes |
After Every 12 Samples |
> |
4000 |
4500 |
1 |
The slowest average portlet response timing for this provider is unacceptable. |
The maximum time (in ms) to request Web provider portlets.
By default, this metric has a critical threshold of 10000 and a warning threshold of 6000. A critical alert is generated when the metric value exceeds the critical threshold value. A warning alert is generated when the metric value exceeds the warning threshold value. You can edit the value for a threshold as required.
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 19-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 15 Minutes |
After Every 12 Samples |
> |
6000 |
10000 |
1 |
The maximum portlet response timing for this provider is unacceptable. |
Indicates whether a specific Web provider has a problem.
By default, this metric has a critical threshold of 'down'. A critical alert is generated when the metric value equals the critical threshold value. You can edit the value for a threshold as required.
By default, Oracle Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
The last response code from the a portlet serviced by this provider is 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 19-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 15 Minutes |
After Every 12 Samples |
= |
Not Defined |
DOWN |
1 |
The last response code from the a portlet serviced by this provider is down. |
User Action
If the status is 'down', it indicates that at least one of the portlets serviced by this provider's last HTTP response code was unsuccessful. Investigate the provider to determine what is causing the fault.
The WSRP Portlet Metric allows you to analyze the performance of individual WSRP provider portlets. For more information about WSRP providers, refer to the Oracle Portal Developer Kit (PDK) page located at http://www.oracle.com/technology/products/ias/portal/pdk.html on the Oracle Technology Network (OTN).
Additional documentation is also available from the Oracle Portal documentation page on OTN located at http://www.oracle.com/technology/products/ias/portal/documentation.html.
|
Note: For target version 10.1.2.5, the collection frequency for each metric is every 15 minutes. |
|
Note: For each metric you can set different warning and critical threshold values for each unique combination of "Portlet Name", "Portlet ID", and "Provider Name" objects.If warning or critical threshold values are currently set for any object, those thresholds can be viewed on the Metric Detail page for this metric. To specify or change warning or critical threshold values for an object, use the Edit Thresholds page. |
Table 19-21 WSRP Portlet Metrics
| Metric | Description |
|---|---|
|
Cache Hits |
Number of times the portlet's content has been serviced by the cache. |
|
Count of HTTP 200 Response codes |
Number of successful requests, that is, HTTP Response and Error Code: 200. |
|
Count of HTTP 400 Response codes |
Number of incomplete requests, that is, HTTP Response and Error Code: 400 |
|
Count of HTTP 500 Response codes |
Number of unsuccessful server errors, that is, HTTP Response and Error Code: 500. |
|
Count of requests which timed out |
Number of requests that timed out |
|
Count of Resolved HTTP 300 Response codes |
Number of successful requests, that is, HTTP Response and Error Code: 300. A portlet that is initially redirected with a 300 response code, may get logged as a 200 response code if it successfully returns content. |
|
Count of Unresolved HTTP 300 Response codes |
Number of unresolved redirects, that is, HTTP Response and Error Code: 300. Of those portlets that returned an HTTP Response Code of 300, this indicates how many redirected requests remain unresolved. For example, an unresolved request gets redirected to another address, that returns an unresolved error code. |
|
Last Response Code |
HTTP response code of the last portlet serviced by the provider. If this response code is not in the 200 or 300 range, this provider may not be providing content to OracleAS Portal. Administrators can use the Portal Developer Kit (PDK) Java test page to check that the machine hosting the provider is accessible and the specific Provider on that machine is working. |
|
Requests |
Number of requests serviced by this WSRP portlet |
|
Slowest Average Portlet Time (msec) |
|
|
WSRP Portlet Average Time (msec) |
Average time (in ms) to request this WSRP portlet |
|
WSRP Portlet Maximum Time (msec) |
Maximum time (in ms) to request this WSRP portlet |
|
WSRP Portlet Minimum Time (msec) |
Minimum time (in ms) to request WSRP portlet |
The average performance of a specific provider's slowest portlet (in ms).
By default, this metric has a critical threshold of 4500 and a warning threshold of 4000. A critical alert is generated when the metric value exceeds the critical threshold value 1 time. A warning alert is generated when the metric value exceeds the warning threshold value. You can edit the value for a threshold as required.
When an alert is generated, the alert text is:
The last response code from the a portlet serviced by this provider is 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 19-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 |
|---|---|---|---|---|---|---|---|
|
10.1.2.5 |
Every 15 Minutes |
After Every 12 Samples |
> |
4000 |
4500 |
1 |
The slowest average portlet response timing for this provider is unacceptable. |
The WSRP Providers metric allows you to analyze the performance of WSRP providers. For more information about WSRP providers, refer to the Oracle Portal Developer Kit (PDK) page located at http://www.oracle.com/technology/products/ias/portal/pdk.html on the Oracle Technology Network (OTN).
Additional documentation is also available from the Oracle Portal documentation page on OTN located at http://www.oracle.com/technology/products/ias/portal/documentation.html.
|
Note: For target version 10.1.2.5, the collection frequency for each metric is every 15 minutes. |
|
Note: For each metric you can set different warning and critical threshold values for each "Provider Name" object.If warning or critical threshold values are currently set for any "Provider 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 "Provider Name" object, use the Edit Thresholds page. |
Table 19-23 WSRP Providers Metrics
| Metric | Description |
|---|---|
|
Cache Hits |
Number of times the Provider's content has been serviced by the cache |
|
Count of HTTP 200 Response codes |
Number of successful requests to portlets, that is, HTTP Response and Error Code: 200 |
|
Count of HTTP 400 Response codes |
Percentage of portlets returning a 400 HTTP Response code - Unsuccessful Request Incomplete |
|
Count of HTTP 500 Response codes |
Number of unsuccessful server errors, that is, HTTP Response and Error Code: 500 |
|
Count of requests which timed out |
Number of requests that timed out |
|
Count of Resolved HTTP 300 Response codes |
Number of successful requests, that is, HTTP Response and Error Code: 300. Note: A portlet that is initially redirected with a 300 response code, may get logged as a 200 response code if it successfully returns content. |
|
Count of Unresolved HTTP 300 Response codes |
Number of unresolved redirects, that is, HTTP Response and Error Code: 300. Of those portlets that returned an HTTP Response Code of 300, this indicates how many redirected requests remain unresolved. For example, an unresolved request gets redirected to another address, that returns an unresolved error code. |
|
Offline |
Indicates if a WSRP provider is currently offline |
|
Percentage of WSRP PRovider HTTP 500 Response codes |
See Section 19.15.1, "Percentage of WSRP Provider HTTP 500 Response codes" |
|
Requests |
Number of requests serviced by this WSRP provider |
|
WSRP Provider Portlets Average Time (msec) |
Average time (in ms) to request WSRP provider portlets |
|
WSRP Provider Portlets Maximum Time (msec) |
See Section 19.15.2, "WSRP Provider Portlets Maximum Time (msec)" |
|
WSRP Provider Portlets Minimum Time (msec) |
Minimum time (in ms) to request WSRP provider portlets |
|
WSRP Provider Status |
The percentage of WSRP Provider requests that returned HTTP 500 response codes, that is, unsuccessful server errors.
By default, this metric has a critical threshold of 15 and a warning threshold of 10. A critical alert is generated when the metric value exceeds the critical threshold value. A warning alert is generated when the metric value exceeds the warning threshold value 1. You can edit the value for a threshold as required.
By default, Oracle Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
The percentage of portlet requests returning unsuccessful is unacceptable for this provider.
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 19-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 |
|---|---|---|---|---|---|---|---|
|
10.1.2.5 |
Every 15 Minutes |
After Every 12 Samples |
> |
10 |
15 |
1 |
The percentage of portlet requests returning unsuccessful is unacceptable for this provider. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Slowest Average Portlet Time (msec)" and "Provider Name" objects.
If warning or critical threshold values are currently set for any unique combination of "Slowest Average Portlet Time (msec)" and "Provider Name" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Slowest Average Portlet Time (msec)" and "Provider Name" objects, use the Edit Thresholds page.
The maximum time (in ms) to request WSRP provider portlets.
By default, this metric has a critical threshold of 10000 and a warning threshold of 6000. A critical alert is generated when the metric value exceeds the critical threshold value. A warning alert is generated when the metric value exceeds the warning threshold value. You can edit the value for a threshold as required.
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 19-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 |
|---|---|---|---|---|---|---|---|
|
10.1.2.5 |
Every 15 Minutes |
After Every 12 Samples |
> |
6000 |
10000 |
1 |
The maximum portlet response timing for this provider is unacceptable. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Provider Name" object.
If warning or critical threshold values are currently set for any "Provider 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 "Provider Name" object, use the Edit Thresholds page.
Indicates whether a specific WSRP provider has a problem.
By default, this metric has a critical threshold of 'down'. A critical alert is generated when the metric value equals the critical threshold value. You can edit the value for a threshold as required.
By default, Oracle Enterprise Manager tests the value of this metric every 10 minutes.
When an alert is generated, the alert text is:
The last response code from the a portlet serviced by this provider is 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 19-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 |
|---|---|---|---|---|---|---|---|
|
10.1.2.5 |
Every 15 Minutes |
After Every 12 Samples |
= |
Not Defined |
DOWN |
1 |
The last response code from the a portlet serviced by this provider is down. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each unique combination of "Slowest Average Portlet Time (msec)" and "Provider Name" objects.
If warning or critical threshold values are currently set for any unique combination of "Slowest Average Portlet Time (msec)" and "Provider Name" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Slowest Average Portlet Time (msec)" and "Provider Name" objects, use the Edit Thresholds page.
User Action
If the status is "down", it indicates that at least one of the portlets serviced by this provider's last HTTP response code was unsuccessful. Investigate the provider to determine what is causing the fault.
