Open odscjames opened 2 years ago
One issue that came up is that the above error was not seen in Sentry. I'm not sure why; sentry is set up for the CLI (just verified). At first I thought it was RQ catching the error and putting it in it's own logs, so sentry doesn't get a chance to see it. Sentry does have RQ integrations that we may have needed - https://docs.sentry.io/platforms/python/guides/rq/ But I tried locally and an error in a task does get reported to sentry without that integration, so I'm not sure what is happening.
Fixed an issue in server monitoring so we get alerts on unhealthy status in future.
Problems were seen with this. The worker had the following Python error repeated:
353 should provide an immediate fix, but making this issue to make work visible and get to the bottom of this.