VeridiumID 3.9.1 allows administrators to change logging levels for supported services directly from Veridium Manager, without restarting the affected application.
Logging can be adjusted for specific packages or classes, allowing administrators to enable detailed diagnostic output for the part of the application being investigated.
Configure logging levels
Runtime logger overrides are configured from:
Veridium Manager → Advanced Settings
The configuration uses JSON entries grouped by service. Each entry specifies the logger to configure and its required logging level.
The following example illustrates the configuration structure:
{
"websec": [
{
"name": "com.example.mypackage",
"level": "DEBUG"
},
{
"name": "com.example.other.SpecificClass",
"level": "TRACE"
}
]
}
The example uses websec as the service key. Replace the com.example... logger names with the relevant package or fully qualified class name for the investigation.
|
Configuration element |
Description |
|---|---|
|
Service key, such as |
Identifies the service whose logger settings are being configured. Its value is a list of logger overrides. |
|
|
Name of the package or class whose logging level should be changed. |
|
|
Logging level to apply to that logger. |
Supported logging levels are:
TRACE, DEBUG, INFO, WARN, ERROR, and OFF.
To apply a change:
-
Open the logger-override configuration in Advanced Settings.
-
Add or update the required logger entries under the applicable service.
-
Set each entry’s
nameandlevel. -
Save the configuration.
VeridiumID validates the configuration and applies valid changes to the running application without requiring a restart. Invalid JSON or an unrecognized logging level produces a validation error in the interface.
Saved overrides and application restarts
Logger overrides are saved and reapplied when the application starts again.
The baseline log4j2.xml configuration remains unchanged. Runtime overrides supplement or override its logger settings without replacing the configuration file.
Important: Restarting the application does not clear saved logger overrides. A diagnostic logging level remains configured until it is changed.
For troubleshooting changes, record the existing logger settings before editing them. When the investigation is complete, restore the intended logging levels and save the configuration again.
Audit and validation
Changes to logger configuration are audit-logged, recording who made the change, what was changed, and when.
Configuration validation checks both the JSON structure and the supplied logging levels, helping administrators identify configuration errors before applying a change.
Scope
This feature controls logging levels. It does not modify or replace log4j2.xml, and it does not configure log output destinations or appenders at runtime.
For downloading logs associated with an identity, device, authentication session, or passkey session, see Admin – Logs Export.