The following describes how to configure monitoring.
To configure monitoring
Navigate to Basic Settings > Alerting & Monitoring.
The default threshold values of the parameters are suitable for most situations. Adjust the threshold values only if needed.
Navigate to Basic Settings > Management and verify that the SNMP settings and Mail settings of SPS are correct. SPS sends alerts only to the alert e-mail address and to the SNMP server.
Sending alerts fails if these settings are incorrect.
The following sections describe the parameters you can receive alerts on.
SPS continuously monitors a number of parameters of the SPS hardware and its environment. If a parameter reaches a critical level (set in its respective Maximum field), SPS sends e-mail or SNMP messages to alert the administrator.
Figure 65: Basic Settings > Alerting & Monitoring — Health monitoring
Disk utilization maximum: Ratio of free space available on the hard disk. SPS sends an alert if the audit trails use more space than the set value. Archive the audit trails to a backup server to free disk space. For details, see Archiving and cleanup.
NOTE: The alert message includes the actual disk usage, not the limit set on the web interface. For example, you set SPS to alert if the disk usage increases above 10 percent. If the disk usage of SPS increases above this limit (for example to 17 percent), you receive the following alert message: less than 90% free (= 17%). This means that the amount of used disk space increased above 10% (what you set as a limit, so it is less than 90%), namely to 17%.
Load average: The average load of SPS during the last one, five, or 15 minutes.
Swap utilization maximum: Ratio of the swap space used by SPS. SPS sends an alert if it uses more swap space than the set value.
Preventing disk space fill-up
The following describes how to prevent disk space from filling up.
NOTE: One Identity highly recommends this if One Identity Safeguard for Privileged Sessions (SPS) is hosted in a virtual environment.
To prevent disk space from filling up
Navigate to Basic Settings > Management > Disk space fill-up prevention.
Figure 66: Basic Settings > Management > Disk space fill-up prevention — Preventing disk space fill-up
Enter the limit of maximum disk utilization in percents in the Disconnect clients when disks are: x percent used field. Make sure to enter a value between 50-98 percent. When disk space is used above the configured limit, SPS disconnects all clients. The default value is 80.
(Optional) To automatically start all configured archiving/cleanup jobs when disk usage goes over the limit, select the Automatically start archiving option.
For more information on configuring an archiving policy, see Archiving and cleanup.
NOTE: If there is no archiving policy configured, selecting this option will not trigger automatic archiving.
Navigate to Basic Settings > Alerting & Monitoring > Health monitoring and enable alert Disk utilization maximum.
System related traps
SPS can send the following system related alerts in e-mail or as SNMP trap. To configure these alerts, see Configuring e-mail alerts and Configuring SNMP alerts.
Figure 67: Basic Settings > Alerting & Monitoring — health monitoring
Table 1: System related traps
||Failed login attempts from SPS web interface.|
||Successful login attempts into SPS web interface.|
|Logout from the management interface
||Logouts from SPS web interface.|
||Any modification of SPS's configuration.|
General alerts and error messages occurring on SPS.
Note that alerts on general alerts and errors are sent whenever there is an alert or error level message in the SPS system log. These messages are very verbose and mainly useful only for debugging purposes.
Enabling these alerts may result in multiple e-mails or SNMP traps sent about the same event.
|Data and configuration backup failed
||Alerts if the backup procedure is unsuccessful.|
|Data archiving failed
||Alerts if the archiving procedure is unsuccessful.|
|Database error occurred
||An error occurred in the database where SPS stores the connection metadata. For assistance, contact our Support Team.|
|License limit reached
||The number of protected servers (or concurrent sessions) reached the limit set in the SPS license. Clients cannot connect to new servers using SPS.|
|HA node state changed
||A node of the SPS cluster changed its state (for example, a takeover occurred).|
|Timestamping error occurred
||An error occurred during the timestaming process (for example, the timestamping server did not respond).|
|Time sync lost
||The system time became out of sync.|
|Raid status changed
||The status of the node's RAID device changed its state.|
|Hardware error occurred
||SPS detected a hardware error.|
|Firmware error occured
SPS detected a firmware error, which can be as follows:
- Corrupted: The firmware integrity check failed. If a firmware is shown as corrupted, contact our Support Team.
- Tainted: It indicates that you have modified a file of the firmware locally. If you have modified a local file unintentionally, contact our Support Team.
|Too many login attempts
||SPS has detected a possible brute-force attack.|
|License expires soon
||Your SPS license will expire within 60 days.|
|A system service failed
A system service has failed.
Note that one alert is sent for each failed service.
|Random generator error occurred
The random generator repeatedly created the same byte sequence. To fix this issue, you can restart your SPS. If the error persists, contact our Support Team.