Error handling and internal state

[Vidar Eldøy]

Error messages are usually handled by lowtide to write to error logs. This does not work though, and is just a bad solution, or at best a last resort.

We need some kind of advanced logging to the database. The error object should be large and contain a snapshot of the internal state at error time. A simple stack trace is not enough. We need to know where it happens, but also have request data included.

Could we design a large object, a new standard error object? This can then be pushed to an app or an API so we can react to errors.

Very often we run things from external scripts too, and we need error handling for that too.