Error handling / events

[iffa]

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. 🙏🏼

[GiovaniGuizzo]

Hey @iffa.

Interesting request. I will talk to @merencia about this, maybe we can come up with something.
There is only one issue, which is that our logger can log errors from the main application or worker threads. We would need to find a way of ensuring all environments accessed the same logger with the same config. This is somewhat possible, but will require some development.

Let me create an issue for that.

[frederikheld]

For anyone who doesn't come from that issue but wants to go there 👉 #118