Read Tomcat Logs after 2025.1 upgrade

Context

2025.1 made a lot of changes regarding log generation. Allowing users and support agent to be more efficient in the search of issues.

The 360Suite Tomcat will now generate new files if old one are getting too large, this will only happen on 360Suite embedded Tomcat. 

The files will have a name like : 360Suite-<date>-<number of file this day>.txt

Where <number of file this day> starts from 1, and goes up for every new file created.

How To

To leverage the new logs, we formatted them in a logical way to allow the usage of third-party tools to read the logs.
In this example we are using ULogViewer, an opensource tool that you can find here.

When given a template, the log file will look like this :

The tool also allow us to filter types of logs, to only search for Errors, specific times and so on.

To apply the template, simply copy everything from the .json file here, and copy it in a file named 360suite.json and you will be able to use it on your own.

Once the template is applied, simply open the log file, and you should see the interface as above.

• Related Articles

• 360Suite database configuration is not set when restarting Tomcat server

  Symptoms On application startup, a warning popup appears In the Administration console, the database configuration is empty even though is was setup previously Environment 360Suite Web Platform Linux server (all) Additional symptoms : tomcat logs In ...

• Change Tomcat after 2025.1 upgrade

  Context To prepare for BI 2025 moving away from Java 8, we migrated from Java 8 to Java 21. This migration impacts everyone doing update from previous version, as the version used for Tomcat is not compatible anymore, as Java 21 requires a Tomcat 10 ...

• Tomcat memory issue

  Symptoms Relevant information: Error about memory issue in a 360Suite task Error message(s): "java.lang.OutOfMemoryError: GC overhead limit exceeded" Information location: Visible in the task logs and / or the tomcat logs Environment Product: ...

• Unable to start 360Suite when tomcat uses slf4j

  Symptom tomcat root page is available /360suite url returns 404 error in tomcat/logs/localhost-{date}.log an error appears on 360Suite startup 03-May-2021 07:51:22.858 SEVERE [localhost-startStop-1] ...

• What are the proper steps to set up the Tomcat service account for Web Platform?

  Symptom How to configure 360Suite Web Platform to use a Windows domain service account to run the 360Suite Windows Service, if it is not an Administrator on the server, i.e. the Tomcat user? Environment 360Suite Web Platform Cause The issue is ...