Skip to content

Improve logging #21

@AksonovSergei

Description

@AksonovSergei

The logging should be improved in this project.
Requirements:

  1. Logging framework glog must be used.
  2. The following log levels should be supported:- ERROR - When an operation fails that could prevent the application from continuing, like a failed network connection.
  • WARNING - When a non-critical operation fails or when something that might lead to a problem in the future happens, like wrong package size received.
  • INFO - When a task starts, ends, or an important milestone is reached, like "Client connected".
  • DEBUG - Used to log detailed information that is useful for debugging the application. These messages provide an in-depth look at the program's internal workings, typically including variable values, flow control, and function calls.
  1. User should be able to change log level using command line options.
  2. The default log level INFO.
  3. Logging should be done to afile.
  • For each program start the new log file should be used.
  • File name should have the following template: kpi-rover-ecu_<yyyymmdd_hhmmss>.log
  • All logs should be saved in the folder: ./log/
  1. It should be possible to enable logging to terminal using command line option. By default logging to terminal should be disabled.
  2. Enter to each function and passed parameters must be logged with log level DEBUG
  3. Return Value from each function must be logged with log level DEBUG

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions