Logs Consultation

Summary

  • The Log Consultation interface allows you to view and manage the event logs of the current module directly from the web interface, without requiring access to the machines.

  • From this interface, administrators can:

    • View in real time the application’s event stream.

    • Modify logging levels (loggers) on the fly to facilitate debugging.

    • Download the current log file for local analysis.

Access to log consultation is restricted to administrators of modules that provide the feature (Console or Marketplace).

The "Administrator" role is the only one among the possible roles for a user sufficient to access this interface.

Log stream

The Log stream tab allows you to monitor application activity in real time. It is the preferred tool for observing the application’s behavior following a specific action.

It is accessible via the "Administrator" button in the side menu of the current module (Console or Marketplace).

From this area, it is possible to control the stream display:

  • Filter by severity : with a simple click on the badges (ERROR, WARN, INFO, DEBUG, TRACE) to display only the levels that interest you.

  • Search : by using the Search in logs…​ field to quickly isolate specific requests, tasks, or errors.

  • Clear display : The Clear all button empties the visual console (this action does not delete the logs, which can be displayed again using the "Stop" then "Start" buttons at any time).

Download logs

If the investigation requires external tools or sending the log to support, the Download button (top right) allows you to retrieve the entire current log file of the opened module and save it locally.

Logger Configuration

The Loggers tab (event generators in the log) allows assigning events from different components and libraries of the module (e.g., org.hibernate.SQL, com.adb.dc) to different severity levels to identify them more easily and facilitate debugging.

Display order

The list of loggers is not strictly alphabetical. The display order is optimized as follows:

  1. Priority loggers : The most critical loggers for the system appear first.

  2. Manually configured loggers : Loggers whose level has been explicitly overridden (not inherited) follow, in alphabetical order.

  3. Other loggers : The rest of the application components, in alphabetical order.

Modify a logger’s severity level

The configuration table presents two key pieces of information for each logger:

  • Effective level : The currently active log level (it may be inherited from a parent package).

  • Configured level : The explicit setting applied to this specific logger.

To modify a behavior, choose the desired level from the dropdown menu (TRACE, DEBUG, INFO, WARN, ERROR or - inherited - to reset).

Click the Apply button in the Action column to save the modification. It takes effect instantly.

Dernière mise à jour le 28 avril 2026 à 11:53