Accessing application log files

Log files are classified according to the following rules:

  • IBM Process Mining application logs (for example, REST API monitoring, application errors, and configuration errors)

  • Categories

    • Front-end and Rest API
    • <PM_HOME>/repository/logs/pm-web.log
    • BPA and IBM Process Mining backend
    • <PM_HOME>/repository/logs/engine.log
    • <PM_HOME>/repository/logs/engine-perf.log
    • Analytics backend
    • <PM_HOME>/repository/logs/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-eureka.log
    • Monitor backend
    • <PM_HOME>/repository/logs/monitoring-perf.log
    • <PM_HOME>/repository/logs/monitoring.log
  • Rolling Policy

    • Files are archived daily by following a rolling policy as shown in the following example:
      pm-web-2019-07-29.0.log
      
  • File retention is 30 days.

  • 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

Tips: You can change the log retention period by changing the maxHistory variable. Similarly, 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 maybe the following values: - ERROR - WARN - INFO - DEBUG

For production environments, it is highly recommended to not set the log level under "INFO".

  • Application Server logs (for example, problems with binding ports, Java version, and generic errors)

    • <PM_HOME>/jetty-web/logs/
    • <PM_HOME>/jetty-engine/logs/
    • <PM_HOME>/jetty-analytics/logs/
  • Web Server logs (NGINX, for web access monitoring)

    • /var/log/nginx/access.log
    • /var/log/nginx/error.log