Get Live Help
Figure 317: Basic Settings > Dashboard > Load average
The Load average module on the Dashboard is based on data provided by the Linux kernel (/proc and /sys directories). The standard Munin plugins query this information from these locations and they are displayed on the GUI.
A measure of the amount of computational work that a computer system performs. The load average represents the average system load over a period of time. It conventionally appears in the form of three numbers which represent the system load during the last one-, five-, and fifteen-minute periods.
The load average types displayed are the following:
Load 1: Average load in 1 minute.
Load 5: Average load in 5 minute.
Load 15: Average load in 15 minute.
Figure 318: Basic Settings > Dashboard > Number of processes
The Number of processes module on the Dashboard is based on the output of the ps command.
The process types displayed are the following:
Processes: Number of running processes.
Forks: Number of forks (system calls). It is an operation where a process creates a copy of itself.
Context switches: Number of context switches. It is the switching of the CPU from one processor thread to another.
Interrupts: Number of interrupts.
The following describes how to display statistics of a specific connection policy.
To display statistics of a specific connection policy
Navigate to Basic Settings > Dashboard > Connection statistics.
To display the statistics of a connection policy, enter the name of the policy into the Connection.
Select the time period to display from the Select resolution field.
Click View graph.
The following sections help you to solve problems related to High Availability clusters.
For a description of the possible statuses of the One Identity Safeguard for Privileged Sessions (SPS) cluster and its nodes, the DRBD data storage system, and the heartbeat interfaces (if configured), see Understanding One Identity Safeguard for Privileged Sessions (SPS) cluster statuses.
To recover a cluster that has broken down, see Recovering One Identity Safeguard for Privileged Sessions (SPS) if both nodes broke down.
To resolve a split-bran situation when the nodes of the cluster were simultaneously active for a time, see Recovering from a split brain situation.
To replace a broken node with a new appliance, see Replacing a HA node in a One Identity Safeguard for Privileged Sessions (SPS) cluster.