Closed scott-r closed 7 months ago
Note that this mechanism should be used for unexpected errors such as assertion failures, inability to access network services, etc. It should not be used for normal runtime errors (e.g. mistyped client id) or debug tracing.
Currently, the app can display error messages on the browser console and the print server writes them to a log file. The browser console is not persistent, and neither source is remotely accessible. We need a new mechanism to store error messages (with timestamps) in a database table. Like the print queue for receipts, it should be accessible via a REST API without authentication so that it can be used by the print server and can record failures when authenticating the the database.