search

VISAB-ORG / VISAB

VISAB is a standalone utility to visualize artificial intelligence agent behavior in games.
1 stars 0 forks source link

F logging capability #22

Closed leRoe93 closed 3 years ago

leRoe93 commented 3 years ago

Logging via args4j is now integrated into the project.

Current setting is that INFO, WARN, ERROR, FATAL are displayed on the console and all levels including DEBUG and trace are written to a visab.log file in parallel.

visab.log is always the recent log file for a daily basis or excess of file size (500mb - pretty big). If a new log gets generated either for time based or size based trigger, the last visab.log will be saved with a timestamp to keep it in the visablogs directory (which is currently the base dir for logs).

All System.out and System.err streams got replaced with logging calls and any class that may need some logging has now a logging object instantiated - please feel free to use it excessively during this project.

General indication of log levels can be found here: https://www.tutorialspoint.com/log4j/log4j_logging_levels.htm

mfroeh commented 3 years ago

Nice, looks good! :rocket: I think we should name the log directory log instead due to

  1. If its in the VISAB application, we already know its logs for VISAB.
  2. We have singular names for our directories (src, bin, repository, ...)

Also it appears that your formatter was set to tabs.

mfroeh commented 3 years ago

I just formatted the entire source again in b581a33 since I know you are busy. Can merge this now whenever you feel like.

leRoe93 commented 3 years ago

Thanks for that!