Accessing application log files
Log files are grouped by using the following rules:
- IBM Process Mining application logs
- Categories
- Rolling Policy
Log files grouped by IBM Process Mining application logs can be sorted as, for example, REST API monitoring, application errors, or configuration errors.
Categories
You can access application log files grouped by following categories:
-
Front-end and Rest API
<PM_HOME>/repository/logs/pm-app-web.log
<PM_HOME>/repository/logs/pm-app-analytics.log
<PM_HOME>/repository/logs/pm-app-bpa.log
<PM_HOME>/repository/logs/pm-app-connectors.log
<PM_HOME>/repository/logs/pm-app-user-management.log
-
IBM Process Mining backend
-
Process discovery backend
<PM_HOME>/repository/logs/pm-engine-process-discovery.log
<PM_HOME>/repository/logs/engine-perf.log
-
BPA backend
<PM_HOME>/repository/logs/pm-engine-bpa.log
-
Analytics backend
<PM_HOME>/repository/logs/pm-engine-analytics.log
<PM_HOME>/repository/logs/analytics-perf.log
-
Accelerator backend
<PM_HOME>/repository/logs/pm-accelerator-core.log
<PM_HOME>/repository/logs/pm-accelerator-sap-p2p.log
<PM_HOME>/repository/logs/pm-accelerator-custom.log
<PM_HOME>/repository/logs/pm-accelerator-custom-std.log
<PM_HOME>/repository/logs/pm-eureka.log
-
Connectors backend
<PM_HOME>/repository/logs/pm-engine-connectors.log
-
Decision rules backend
<PM_HOME>/repository/logs/pm-engine-decision-rules.log
-
Monitor backend
<PM_HOME>/repository/logs/monitoring-perf.log
<PM_HOME>/repository/logs/pm-engine-monitoring.log
Rolling Policy
Files are archived daily by following a rolling policy as shown in the following example:
pm-app-web-2024-04-22.0.log
The file storage period is 30 days.
The maximum file size is 50 MB.
Log Settings
The application logs settings are available in the following files:
/etc/logback-web.xml
/etc/logback-engine.xml
/etc/logback-analytics.xml
You can change the log retention period by changing the maxHistory
variable.
You can change the maximum file size by changing the maxFileSize
variable in the application logs settings files.
The <logger>
element contains the log level with the following possible values:
- ERROR
- WARN
- INFO
- DEBUG
Only set the log level under INFO value in the production environments if necessary.
You can access logs to the following servers:
- Application Server logs
<PM_HOME>/jetty-web/logs/
<PM_HOME>/jetty-engine/logs/
<PM_HOME>/jetty-analytics/logs/
You can use these logs to learn about:
- Problems with binding ports.
- Java version.
- Generic errors.
- Web Server logs
/var/log/nginx/access.log
/var/log/nginx/error.log
You can use these logs to:
- view NGINX settings.
- monitor web access.