Analyzing Logs

All services running on the PAS platform, and the platform services themselves, write log messages. In particular, xUML services write messages to a service log and a transaction log (if configured). You can use the Log Analyzer to analyze these logs.

All logging information from the various sources is saved as documents to OpenSearch. You can use the Log Analyzer, in addition to the Resource Monitor, to analyze the logs of faulty services and find solutions for problematic behavior.
The Log Analyzer uses OpenSearch as data storage and OpenSearch Dashboards to analyze the service logs. OpenSearch Dashboards is an open source analytics and visualization tool. You can search, view, and interact with data stored in OpenSearch indices. You can perform advanced data analysis and visualize your data in a variety of charts, tables, and maps in customized dashboards.

The retention time for logs in the Log Analyzer is 30 days.

The pages in this chapter explain the contents of the log files, and how to use the Log Analyzer to find information about service behavior.

Usage Example

• A service crashes periodically.

• A service shows error messages during execution.

Use the Log Analyzer to check whether certain faulty service behavior or error messages in the UI correlate with errors in the service logs.

Use the Resource Monitor to check if error messages in the log correlate with periods of high load or memory usage. It also shows you the load a service causes and the memory usage of the service. You can check whether defined limits are repeatedly exceeded - and react accordingly.
Refer to Monitoring Container Activities for details.
In this case, you could e.g. go to the service details in the PAS Administration, and adapt the memory limit of the service. Depending on your setup, refer to Docker: Adapting the Configuration of Containerized xUML Services or Kubernetes: Adapting the Configuration of Containerized xUML Services.

Related Content