|
Oracle® Enterprise Manager Metric Reference Manual
10g Release 1 (10.1) Part No. B12015-01 |
|
|
|
|
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 name of the Oracle Database where the OracleAS Portal schema is running.
Shows the time the Oracle Database was last started.
The Database Portlet metric allows you to analyze the performance of individual database portlets. For more information about database portlets, refer to the OracleAS Portal Developer Kit (PDK) documentation at http://portalstudio.oracle.com.
Additional OracleAS Portal documentation is also available in the documentation section on Portal Center at http://portalcenter.oracle.com.
The number of times database portlet content has been serviced by the cache.
The number of successful requests, i.e. HTTP Response and Error Code: 200.
The number of incomplete requests, i.e. HTTP Response and Error Code: 400.
The number of unsuccessful server errors, i.e. HTTP Response and Error Code: 500.
The number of requests to this database portlet that timed out.
The number of successful requests, i.e. 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.
The number of unresolved redirects, i.e. 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.
The average time (msec) to request this database portlet.
The maximum time (msec) to request this database portlet.
The minimum time (ms) to request this database portlet.
The http response code of the last database portlet serviced by the provider.
The Database Providers metric allows you to analyze the performance of database providers. For more information about Database Providers, refer to the OracleAS Portal Developer Kit (PDK) documentation at http://portalstudio.oracle.com.
Additional OracleAS Portal documentation is also available in the documentation section on Portal Center at http://portalcenter.oracle.com.
The number of times the database provider�s content has been serviced by the cache.
The number of successful requests, i.e. HTTP Response and Error Code: 200.
The number of incomplete requests, i.e. HTTP Response and Error Code: 400.
The number of unsuccessful server errors, i.e. HTTP Response and Error Code: 500.
The number of requests that timed out.
The number of successful resolved requests, i.e. 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.
The number of unresolved redirects, i.e. 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.
The average time (in ms) to request database portlets.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-1 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 15 Minutes | After Every 12 Samples | > | 4000 | 4500 | 1 | The slowest average portlet response timing for this provider is unacceptable. |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The maximum time (in ms) to request database portlets.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-2 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 15 Minutes | After Every 12 Samples | > | 6000 | 10000 | 1 | The maximum portlet response timing for this provider is unacceptable. |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The minimum time (in ms) to request database portlets.
Indicates whether a specific database provider has a problem.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-3 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| 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. |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
Indicates whether the database provider is currently offline.
The percentage of Database Provider requests that returned HTTP 500 response codes, i.e. unsuccessful server errors.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-4 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 15 Minutes | After Every 12 Samples | > | 10 | 15 | 1 | The percentage of portlet requests returning unsuccessful is unacceptable for this provider. |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The General Page Engine metric allows you to analyze the performance of your portal's Parallel Page Engine.
The average number of requests in the Parallel Page Engine internal portal content request queue, since middle tier startup.
The average time (in ms) content requests have spent in the Parallel Page Engines internal request queue.
The number of requests for fully cached pages that resulted in content being returned from the cache since middle tier startup.
The percentage of requests for cacheable, fully assembled pages that resulted in a cache hit.
The percentage of OracleAS Portal content requests that have timed out in the Parallel Page Engine's internal request queue.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-5 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 10 Minutes | After Every 12 Samples | > | 10 | 15 | 1 | The percentge of requests that have timed out in the internal request queue is unacceptable. |
The number of requests for cached enabled pages since middle tier startup.
The number of requests for cacheable, fully assembled pages since middle tier startup.
The Page Engine Response Code metrics provide HTTP response code information.
The percentage of portlets returning a 200 HTTP Response code - Successful Request.
The 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.
The 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.
The percentage of portlets returning a 400 HTTP Response code - Unsuccessful Request Incomplete.
The percentage of portlets returning a 500 HTTP Response code - Unsuccessful Server Errors.
The number of timeouts registered by the Parallel Page Engine.
The number of successful requests to portlets, i.e. HTTP Response and Error Code: 200.
The number of successful resolved requests to portlets, i.e. 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.
The number of unresolved redirects from portlet requests, i.e. 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.
The number of incomplete requests to portlets, i.e. HTTP Response and Error Code: 400.
The number of unsuccessful server errors, i.e. HTTP Response and Error Code: 500.
The total number of portlets requested 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.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-6 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every 12 Samples | > | 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.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-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 | =
|
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
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-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 | 0 | 1 | The Portal instance is not accessible. |
The Syndication Server Status Metric provides status information for the Syndication Server.
If the status value is '1', the Syndication Server is available.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-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 | =
|
Not Defined | 0 | 1 | The Syndication Server is not accessible. |
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 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.
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.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-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 |
|---|---|---|---|---|---|---|---|
| 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 OracleAS Portal Developer Kit (PDK) documentation at http://portalstudio.oracle.com.
Additional OracleAS Portal documentation is also available in the documentation section on Portal Center at http://portalcenter.oracle.com.
The number of times the portlet's content has been serviced by the cache.
The number of successful requests, i.e. HTTP Response and Error Code: 200.
The number of incomplete requests, i.e. HTTP Response and Error Code: 400.
The number of unsuccessful server errors, i.e. HTTP Response and Error Code: 500.
The number of requests that timed out.
The number of successful requests, i.e. 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.
The number of unresolved redirects, i.e. 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.
The HTTP response code of the last portlet serviced by the provider.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
If this response code is not in the 200 or 300 range, this provider may not be providing content to OracleAS Portal.
The administrator should check that the machine hosting the provider is accessible, and the specific Provider on that machine is working by using the PDK Java test page.
The number of requests made to this Web portlet.
The average time (in ms) to request this Web portlet.
The maximum time (in ms) 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 OracleAS Portal Developer Kit (PDK) documentation at http://portalstudio.oracle.com.
Additional OracleAS Portal documentation is also available in the documentation section on Portal Center at http://portalcenter.oracle.com.
The number of times the Provider's content has been serviced by the cache.
The number of successful requests to portlets, i.e. HTTP Response and Error Code: 200.
The percentage of portlets returning a 400 HTTP Response code - Unsuccessful Request Incomplete.
The number of unsuccessful server errors, i.e. HTTP Response and Error Code: 500.
The number of requests that timed out.
The number of successful requests, i.e. 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.
The number of unresolved redirects, i.e. 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.
Indicates if a Web provider is currently offline.
The percentage of Web Provider requests that returned HTTP 500 response codes, i.e. unsuccessful server errors.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-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 15 Minutes | After Every 12 Samples | > | 10 | 15 | 1 | The percentage of portlet requests returning unsuccessful is unacceptable for this provider. |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The number of requests serviced by this Web provider.
The average time (in ms) to request Web provider portlets.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-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 15 Minutes | After Every 12 Samples | > | 4000 | 4500 | 1 | The slowest average portlet response timing for this provider is unacceptable. |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The maximum time (in ms) to request Web provider portlets.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-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 15 Minutes | After Every 12 Samples | > | 6000 | 10000 | 1 | The maximum portlet response timing for this provider is unacceptable. |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The minimum time (in ms) to request Web provider portlets.
Indicates whether a specific Web provider has a problem.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 13-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 15 Minutes | After Every 12 Samples | =
|
Not Defined | DOWN | 1 | The last response code from the a portlet serviced by this provider is down. |
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. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.