Loggers
The Loggers page shows the logging level of every logger and logger group in a Spring Boot instance and lets you change it at runtime, permanently or for a limited time.
Loggers page as presented in Axelix UI
To investigate a problem on a running service, you often need more detailed logs from one part of it. The Loggers page lets you raise the level of a logger right away, without changing the configuration or restarting the service, and then bring it back.
The page is available to every authenticated user: VIEWER, EDITOR, ADMIN, and SUPER_ADMIN can all open it, change levels, and reset levels. See Roles and authorities for the full role/authority matrix.
What the page shows
The page lists all loggers and logger groups of the instance with their current level. A target mark 
next
to a level means the level is set explicitly for this logger or group, in the application configuration or in Axelix.
A level without the mark is inherited from a parent logger.
next
to a level means the level is set explicitly for this logger or group, in the application configuration or in Axelix.
A level without the mark is inherited from a parent logger.You can change the level:
- Of a logger. Its children without their own level inherit the new level: when you switch
com.axelixlabs.axelixfrom INFO to DEBUG,com.axelixlabs.axelix.sbsswitches to DEBUG as well. - Of a logger group. The level applies to every logger in the group: setting the
webgroup to WARN sets WARN for all of its loggers.
The reset button 
returns a logger to the level it had before you first changed it in Axelix. It works for loggers changed at
runtime: on this page, through MCP, or with a direct request to the axelix-loggers actuator endpoint. Logger groups
cannot be reset.
Temporary logging level
Setting a temporary logging level in Axelix UI
When you need verbose logs only for a while, for example to catch a bug, set a temporary level instead and don't worry about switching it off. Click the timer icon next to the logger, pick the level and the time when it should end. If that time has already passed today, the level stays until that time tomorrow.
When the time runs out, the logger returns to the level it had before. To end the temporary level early, reset the logger. Temporary levels are not available for logger groups.
MCP Tools
Reading the logger tree and changing levels at runtime (for a single logger, a logger group, or resetting an individual logger) are also exposed to AI agents through MCP. See the MCP Tools catalog.
Enable Dedicated Actuator Endpoint
If you are on Axelix 1.2.0 or later, none of this is required: the starter registers its custom actuator endpoints by itself, and Axelix no longer requires the health/info endpoints to be enabled — it works perfectly well without them. No configuration is needed here.
The page is backed by the axelix-loggers actuator endpoint contributed by the Axelix Spring Boot Starter. Expose it
through the standard Spring Boot Actuator properties — see Configuring Spring Boot
Starter for the full
list of Axelix endpoints and surrounding setup:
management.endpoints.web.exposure.include=axelix-loggers