Log4J Loggers
Page reserved for super administrators (members of the GROUP_ALFRESCO_ADMINISTRATORS group).
Purpose of this page
Alfresco uses Log4J as its logging library (recording technical events to log files). This page lets you view and change, without restarting the server, the detail level of the logs produced by any logger (the name of a log channel, typically a Java package or class) — useful to temporarily get more detailed logs while diagnosing an issue, without editing a configuration file on the server.
Accessing the page
Pristy Portail menu: OOTBee Support Tools > Log4J Loggers.
Search and filters
- A search field filters loggers by name (search triggers after a short typing pause).
- The Show unconfigured loggers toggle also displays loggers that only inherit their level from a parent, in addition to explicitly configured ones.
- The table is paginated (20, 50 or 100 rows per page).
Table columns
| Column | Description |
|---|---|
| Name | Logger name (typically a Java package or class); the inherited parent logger’s name shows below it when applicable |
| Level | Level explicitly configured for this logger, editable directly via a dropdown: TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF, or UNSET (no own level, inherits from parent) |
| Effective Level | Level actually applied once inheritance is resolved (read-only) |
| Action | Reset button, active only for loggers that can be reset |
Changing a logger’s level
Select the new level directly from the Level dropdown; the change applies immediately, with no further confirmation, and a message confirms the operation.
Adding a logger
The Add Logger button opens a dialog to enter the logger’s fully qualified name (e.g. an Alfresco package name) and the desired level, then confirm.
Resetting a logger
The button in the Action column resets an individual logger (after confirmation); the Reset All button at the top of the page resets every configured logger in a single action (after confirmation, flagged as a sensitive action).
[To verify] The exact effect of a reset (reverting to the server’s startup configuration versus simply clearing the in-memory override) could not be confirmed in the reviewed code, nor could the persistence of level changes across a server restart.
Last Update - October 20, 2026