27 Single Sign-On Server

You can use the Single Sign-On Server metrics to monitor load and user activity on the OracleAS Single Sign-On Server. Statistics are for the previous 24 hours.

Login Server Metrics For The Last 24 Hours

These Login Server metrics provide information about login activity on the OracleAS Single Sign-On Server over the last 24 hours. The following table lists the metrics and their descriptions.

Note:

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

Table 27-1 Login Server MEtrics For The Last 24 Hours

Metric	Description
Number of Login Attempts	Total number of login attempts over the last 24 hours
Number of Successful Login Attempts	Total number of successful login attempts over the last 24 hours
Number of Unsuccessful Login Attempts	Total number of unsuccessful login attempts over the last 24 hours
Percentage of Successful Logins	Percentage of successful login attempts over the last 24 hours
Percentage of Unsuccessful Logins	Percentage of unsuccessful login attempts over the last 24 hours

Login Server Metrics For The Last Hour

These metrics provide information about login activity on the OracleAS Single Sign-On Server over the last hour. The following table lists the metrics and their descriptions.

Note:

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

Table 27-2 Login Server MEtrics For The Last 24 Hours

Metric	Description
Number of Login Attempts	Total number of login attempts over the last hour
Number of Successful Login Attempts	Total number of successful login attempts over the last hour
Number of Unsuccessful Login Attempts	Total number of unsuccessful login attempts over the last hours
Percentage of Successful Logins	Percentage of successful login attempts over the last hour
Percentage of Unsuccessful Logins	Percentage of unsuccessful login attempts over the last hour

Most Failed Login Users Metrics

The Most Failed Login Users Metrics provide detailed information about each failed login attempt, including the time when the failure happened and the IP address of the machine where the user attempted to login.

Note:

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

Table 27-3 Most Failed Login Users Metrics

Metric	Description
Frequency	Number of times a user has failed to login during the previous 24 hours
Subscriber ID	Subscriber ID of the user trying to log in
Subscriber Name	Subscriber name of the user trying to log in

SSO Database Instance Metric

The Database Instance metric provides information about the Oracle Database that the OracleAS Single Sign-On Server schema is running on. The following table lists the metrics, descriptions, and data source.

Note:

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

Table 27-4 SSO Database Instance Metrics

Metric	Description	Data Source
Instance Name	Name of the Oracle Database where the OracleAS Portal schema is running.	instance_name in the v$instance table
Start Time	Time at which the Oracle Database was last started	startup_time from the v$instance table
Version	Version of the Oracle Database being used	version from the v$instance table

SSO Status Metric

The SSO Status metrics allow you to monitor the status of the OracleAS Single Sign-On Server.

Status

Indicates whether the Single Sign-On Server is 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 27-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	=	Not Defined	0	1	The SSO instance is not accessible.

Data Source

This status test involves pinging a package on the Single Sign-On Server schema using mod_plsql.

User Action

If this status test fails, it indicates that there is an issue with one or more of the components that the Single Sign-On Server depends on. For example, the Single Sign-On Server Database Access Descriptor (DAD) may have an incorrect password, the Oracle HTTP Server may be down, or the Oracle Database the schema is running on may be unaccessible.