In addition to the monitoring tools in SPP, you can use the SPP to One Identity Safeguard for Privileged Sessions (SPS) join issues during the join process. Several SPS tools are described below.
Join process fails and real-time monitoring
If the join process fails for any reason, consult the system logs.
To view the Safeguard for Privileged Sessions logs, navigate to Basic Settings | Troubleshooting | View log files.
To show only the logs for the join process:
- Select a Logtype of syslog.
- Select the Day; today is the default.
- In the Show only messages containing text box, enter SPP-join.
Use the buttons at the bottom of the dialog to perform the following tasks:
- To download the log file, click Download.
- To follow the current log messages real-time, click Tail. The latest logs will update in a browser window while you interact with the join process.
- To display the log messages, click View.
To increase the level of detail in the log, enable debug level logging at Basic Settings | Management | Debug logging | Enable debug logs.
Join successful but connections do not work
When SPP and SPS report a successful join, but the connections don't work, view the SPS connection logs.
In Safeguard for Privileged Sessions, navigate to Basic Settings | Troubleshooting | View log files.
To show only the logs for the join process:
- Select a Logtype of ssh or rdp.
- Select the Day (today is the default).
- In the Show only messages containing text box, enter SPP-join.
To change the verbosity level of SPS, complete the following steps in Safeguard for Privileged Sessions:
- Navigate to the Global Options page of the traffic for which you want to change the log level. For example, go to SSH Control | Global Options to change the log level of SSH traffic, RDP Control | Global Options for remote desktop traffic, and so on.
-
Select the desired log level from the Verbosity level field. The verbosity level ranges from 1 (no logging) to 10 (extremely detailed), with level 4 being the default normal level.
|
|
CAUTION: High verbosity levels generate a very large amount of log messages and might result in a very high load on the machine. Log levels set around 9 to 10, may result in logs with highly sensitive data, for example, passwords in plain text format. |
Testing network issues
You can use the Diagnostics tools of SPP and SPS to test network issues. The following commands are available:
- ping: Sends a simple message to the specified host to test network connectivity.
- traceroute: Sends a simple message from SPS to the specified host and displays all hosts on the path of the message. It is used to trace the path the message travels between the hosts.
- connect: Attempts to connect the specified host using the specified port. It is used to test the availability or status of an application on the target host.
To execute one of the above commands on SPS, see Network troubleshooting.
To execute one of the above commands on SPP, see Diagnostics tools of SPP.
Creating an SPS Support Bundle
If you have an issue which needs Support assistance, you may be asked to provide an SPS Support Bundle. To collect system-state information (also known as a debug bundle) in One Identity Safeguard for Privileged Sessions, see Collecting logs and system information for error reporting.