Currently, local server commands (CLI commands issued on the Rabbit), are logged to the commands.log file. This is useful for analysis but is another location that must be checked for any failure while debugging
With the introduction of structured logging in NearNodeFlash/nnf-ec#71 , we should instead use the ec.Logger and various log levels to trace the server commands and failures. Examples are included in the nnf, nvme, and fabric managers.
Suggested verbosity levels are:
Info V(0) - Always on (unless explicitly disabled)
Confirmation that various initialization (run once) operations succeeded (not per object/resource events - these can fill the logs)
Events that are unusual, but recoverable.
Debug V(1) - On during development, Off in production
Confirmation that various per-resource operations succeeded. i.e. Created an VG/LV, Mounted/Unmounted.
Verbose V(2) - On during early development, Off otherwise.
Indication of operations starting i..e Creating a resource
Currently, local server commands (CLI commands issued on the Rabbit), are logged to the
commands.logfile. This is useful for analysis but is another location that must be checked for any failure while debuggingWith the introduction of structured logging in NearNodeFlash/nnf-ec#71 , we should instead use the
ec.Loggerand various log levels to trace the server commands and failures. Examples are included in the nnf, nvme, and fabric managers.Suggested verbosity levels are:
Info V(0) - Always on (unless explicitly disabled)
Debug V(1) - On during development, Off in production
Verbose V(2) - On during early development, Off otherwise.