Currently, the only debug messages we can do without a debugger are prints to stderr or stdout. These are (mostly) inaccessible when running as a systemd service. We need a logging module that can send messages wherever is necessary for ease of debugging.
This should probably start by sending DEBUG packets to the FMS, but the options are expansive.
For instance:
- Send to a log file controlled by the config file
- Send to an OS message queue to be picked up and handled by another process
- Send to an arbitrary network location to be displayed in a debugging program
Different levels of logging messages should be available (e.g. DEBUG, WARNING, ERROR), and we should be able to filter which are actually logged according to the robot configuration.
All of this should eventually be controlled by the config file, and logging messages should be able to call a single "log" function to get their messages out there.
Currently, the only debug messages we can do without a debugger are prints to stderr or stdout. These are (mostly) inaccessible when running as a systemd service. We need a logging module that can send messages wherever is necessary for ease of debugging.
This should probably start by sending DEBUG packets to the FMS, but the options are expansive.
For instance:
Different levels of logging messages should be available (e.g. DEBUG, WARNING, ERROR), and we should be able to filter which are actually logged according to the robot configuration.
All of this should eventually be controlled by the config file, and logging messages should be able to call a single "log" function to get their messages out there.