Logging

Logging Levels

Each Flopsar module (application) uses logging levels. The levels are defined as follows:

debug : more detailed logging than info. Used to log some additional information about the application operation and data processing. Use only in cases when you suspect some problems with the application, want to trace how it processes requests or you are requested by the Flopsar Technology Support to help investigate some problems, or any other problems. It prints lots of diagnostic information, which might not be covered by this manual.

info : default level used in applications. Used only to log some runtime information to verify a configuration and the like. You should use this level on normal, production operation.

warn : used in cases when some error occurs but with no impact on the application stability and data integrity.

error : normally, there should be no error messages in the log. The level is used in cases when some error occurs. These errors impact the application operation stability and data integrity but not all of them. The messages are informative, so you should know whether you can ignore them or not. Any system calls and external libraries errors are also logged in this level.

Messages

All logger messages have the following format:

DATETIME LEVEL [XXXXXXXX] LOG_ENTRY

where:

DATETIME - date time of the log entry,

LEVEL - log level,

XXXXXXXX - first eight characters of the agent instance name,

LOG_ENTRY - log entry

Server

Depending on the selected logger backend, the logs can be access in different ways. If the logger backend is Local, the server logs are stored in the <home_directory>/logs directory. If the backed is Syslog, you can access the logs by executing the command:

$ journalctl -t flopsar -r

Please, refer to the server configuration for more details on its logger settings.