About NuoDB Admin tier logging

NuoDB Admin logging is configured in nuoadmin.conf file.

The root logging level is controlled by logging.defaultLogLevel parameter (by default info). Increasing verbosity of non-root loggers is done by specifying individual loggers and their corresponding log level via logging.logLevels parameter.

Applying the changes of the above parameters requires NuoDB Admin process restart.

The available logging levels in descending order of verbosity are:

Level Description

all

All log messages.

trace

Designates fine-grained informational events that are most useful for low-level debugging purposes.

debug

Designates fine-grained informational events that are most useful for debug purposes.

info

Designates informational messages that highlight the progress of the application at a coarse-grained level.

warn

Designates potentially harmful situations.

error

Designates error events that might still allow the application to continue running.

off

The highest possible rank and is intended to turn off logging.

During normal operations, there is no need to change the default NuoDB Admin logging level.

However, logging can be adjusted as shown in the following examples;

Example 1

To eliminate repetitive INFO messages which can obscure pertinent messages in the log file, apply the following type of configuration construct in nuoadmin.conf. In this example, to switch off "Request Log" messages:

...
"logging.logLevels": {"org.eclipse.jetty.server.RequestLog": "OFF"},
...

Example 2

In rare situations and when instructed by NuoDB Support, more verbose logging for non-root loggers can be configured. For example, to set the logging level for com.nuodb.nagent.ping.service.PingServer logger to debug, apply the following configuration in nuoadmin.conf:

...
"logging.logLevels": {"com.nuodb.nagent.ping.service.PingServer": "debug"},
...

This will emit logging messages using the following format in nuoadmin.log file:

...
2021-03-05T14:28:45.835+0000 INFO  [nuoadmin1:nuoadmin1-pingExecutor1-2] PingServer peer=nuoadmin3 addr=nuoadmin3:48005 ipAddress=172.19.0.4: Connected
2021-03-05T14:28:45.835+0000 INFO  [nuoadmin1:nuoadmin1-pingExecutor1-2] PingServer peer=nuoadmin3 addr=nuoadmin3:48005 ipAddress=172.19.0.4: Connected
2021-03-05T14:28:47.024+0000 DEBUG [nuoadmin1:nthriftserver-port48005-33-2] PingServer Peer nuoadmin2 has matching storage passwords
2021-03-05T14:28:47.024+0000 DEBUG [nuoadmin1:nthriftserver-port48005-33-2] PingServer Peer nuoadmin2 has matching storage passwords
2021-03-05T14:28:47.029+0000 DEBUG [nuoadmin1:nthriftserver-port48005-33-3] PingServer Peer nuoadmin3 has matching storage passwords
2021-03-05T14:28:47.029+0000 DEBUG [nuoadmin1:nthriftserver-port48005-33-3] PingServer Peer nuoadmin3 has matching storage passwords
2021-03-05T14:28:47.511+0000 DEBUG [nuoadmin1:nuoadmin1-pingExecutor1-1] PingServer PH [Peer [serverId=nuoadmin3, th=TH [nuoadmin3:48005]]]: 5.5111 ms
2021-03-05T14:28:47.512+0000 DEBUG [nuoadmin1:nuoadmin1-pingExecutor1-8] PingServer PH [Peer [serverId=nuoadmin2, th=TH [nuoadmin2:48005]]]: 6.1632 ms
2021-03-05T14:28:47.511+0000 DEBUG [nuoadmin1:nuoadmin1-pingExecutor1-1] PingServer PH [Peer [serverId=nuoadmin3, th=TH [nuoadmin3:48005]]]: 5.5111 ms
2021-03-05T14:28:47.512+0000 DEBUG [nuoadmin1:nuoadmin1-pingExecutor1-8] PingServer PH [Peer [serverId=nuoadmin2, th=TH [nuoadmin2:48005]]]: 6.1632 ms
2021-03-05T14:28:47.513+0000 DEBUG [nuoadmin1:nuoadmin1-pingExecutor1-3] PingServer PH [Peer [serverId=nuoadmin1, th=TH [nuoadmin1:48005]]]: 7.4627 ms (SELF)
2021-03-05T14:28:47.513+0000 DEBUG [nuoadmin1:nuoadmin1-pingExecutor1-3] PingServer PH [Peer [serverId=nuoadmin1, th=TH [nuoadmin1:48005]]]: 7.4627 ms (SELF)
...
Increasing logging levels may cause the log file size to increase faster. Ensure that there is enough disk space in the $NUODB_LOGDIR directory.