Error handling / events

Discussed in https://github.com/sidequestjs/sidequest/discussions/117

^{Originally posted by iffa October 11, 2025}
Background information: due to an oopsie of mine, our dev environment had an incorrect Sidequest config for a while which we did not notice because Sidequest's logging calls aren't intercepted by Sentry (and not sure if that's even a possibility). I was hoping to setup at least some form of explicit alerting to Sentry based on e.g. error events or DB connection issues or something similar, but I couldn't find anything in the docs about this. Is it possible to receive events (like engine not being able to start for reason X, job not being able to start due to e.g. incorrect sidequest.jobs.js definition, DB connection failing because of.. etc.)?

I know the "Pro" version down the line will have something like this at least but I do hope that this also finds it way to the basic version, as this is quite important stuff to have even for the most basic production apps. 🙏🏼

Start by reading discussion #117 and inventory the existing error and event handling described there. The issue needs a defined event surface, alerting behavior, and scope for database and startup failures before implementation can begin; done should include agreed behavior and coverage for the supported failure cases.