Logging Microservices

yuuvis® RAD 9.x »

In yuuvis® RAD services-admin, the log level can be set for each microservice via the Logging area.

The packages of the microservices are shown with the current log levels.

Changes are applied instantly, but reset to default log levels after a microservice has been restarted (see below).

The log file is called via the Wallboard > Logging > Logfile area of the 'argus' microservice.

Settings for the Log File

Settings for the log file can be changed via the servicewatcher-sw.yml configuration file from the \services\service-manager\config\ directory.

file: ./../../logs/services.log Name and path of log file
maxDays: 15

Number of days that a log file is stored

maxFileSize: 10MB Maximum size of a log file
totalSizeCap: 30MB

Maximum size of all log files in the directory

Once the maximum size has been reached, the oldest log files are deleted until the value is below the maximum size.

Changes are applied only after a restart.

Default Log Levels

Changes to log levels are reset to default log levels only after a microservice has been restarted. The default log level for the packages can be specified via the entries in configuration files for microservices.

Syntax: logging.level.<Package>: <Level>


The 'search' microservice contains the com.netflix.appinfo.InstanceInfo package with the WARN default log level.

To change the default log level of the package, add the following entry to the search-prod.yml configuration file:

logging.level.com.netflix.appinfo.InstanceInfo: ERROR

Values for log levels: TRACE, DEBUG, INFO, WARN, ERROR

The new default log level becomes active after the microservice has been restarted.

If there is no microservice configuration file, create one in the \services\service-manager\config\ directory and give it the following name: <Microservice name>-prod.yml