This section of the PingIntelligence Monitoring Guide provides administrators with a list of commands that can be used to perform health checks on different PingIntelligence components.
There are multiple methods explained for each component. You can automate the steps or use them in manual mode. The document also captures information on log files, process ID (PID) details, and port details of the API Security Enforcer (ASE) nodes, the API Behavioral Security (ABS) artificial intelligence (AI) engine, and the PingIntelligence Dashboard.
For more information, click the tab for the respective PingIntelligence components:
Performing health checks on ASE
You can use the following options to conduct a health check on ASE nodes:
Performing health checks on the ABS AI engine
Use the following options to conduct a health check on the ABS AI engine:
Performing health checks on the PingIntelligence Dashboard
Use the following commands to check the health status of the PingIntelligence Dashboard and its components:
-
To check the health status of the Dashboard data engine:
-
To check the health status of the WebGUI:
-
To check the health status of Elasticsearch:
-
To check the health status of Kibana:
Logs, port numbers, and process IDs
Review this supplementary information on log file details, important port numbers, and process ID (PID) information of PingIntelligence for APIs components.
Log files
The following table shows the main log files of PingIntelligence components.
ASE | ABS AI Engine | PingIntelligence Dashboard |
---|---|---|
Note:
abs.log must be the first place for debugging any issues on the ABS. The log has information about each machine learning job on the host. All incoming communication from ASE or the PingIntelligence Dashboard or REST API requests are logged in this file. It also has a periodic log on heartbeat to MongoDB. |
|
Port numbers
The following table shows important port numbers used by PingIntelligence components.
ASE | ABS AI Engine | PingIntelligence Dashboard |
---|---|---|
|
PID information
All PingIntelligence components have their respective PID files. Refer to these files for monitoring or for getting the PID information of the processes.
ASE | ABS AI Engine | PingIntelligence Dashboard |
---|---|---|
The ASE PID file contains the PID for the controller process and the HTTP balancer and HTTPS balancer processes: /pingidentity/ase/logs/ase.pid |
The /pingidentity/abs/data/abs.pid file contains the PID for the main ABS process. |
There are separate PID files for the different components of the PingIntelligence Dashboard:
|