You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to implement a logging solution to aid in debugging as well as track the state of the firmware in production. Logging will be performed through a UDP configured socket. In the case that the system is offline (offline detection required), logs will be sent over SPI to the SD card. The logging subsystem will be provisioned a single socket for logging.
The production systems will be a logging client streaming logs to a log aggregator such as Loki. Debug releases will have a socket server which can be connected to in order to view the active logs:
Description
We need to implement a logging solution to aid in debugging as well as track the state of the firmware in production. Logging will be performed through a UDP configured socket. In the case that the system is offline (offline detection required), logs will be sent over SPI to the SD card. The logging subsystem will be provisioned a single socket for logging.
The production systems will be a logging client streaming logs to a log aggregator such as Loki. Debug releases will have a socket server which can be connected to in order to view the active logs:
socat - UDP:192.168.2.34:4000 1643325325.55223 DEBUG main:10 Executing scheduled state caching job 1643325326.46846 CRITICAL eeprom_read:18 EEPROM read to address 0x56 failed ...
The text was updated successfully, but these errors were encountered: