Log failed jobs in separate directory #5

New Issue

erth9960 · 2021-10-26T09:44:08+02:00

erth9960 commented

2021-10-26 09:44:08 +02:00

Currently the application has no idea whether a queue item has failed before or not. It will simply consume any queue items and skip ones that fail, while notifying the administrator.

This behaviour makes monitoring more difficult, since it's impossible to see whether a queue item has failed or not.

A new support directory should be defined in the [daemon] section of config.ini as error = /somepath. Any errors for a specific job that get emailed should also be saved to a file in the error directory. The filename should be the same as the job file name.
If there is error information in place already when saving a new error it can be overwritten.

Any corresponding uploaded files should be left in place.

Currently the application has no idea whether a queue item has failed before or not. It will simply consume any queue items and skip ones that fail, while notifying the administrator. This behaviour makes monitoring more difficult, since it's impossible to see whether a queue item has failed or not. A new support directory should be defined in the `[daemon]` section of config.ini as `error = /somepath`. Any errors for a specific job that get emailed should also be saved to a file in the `error` directory. The filename should be the same as the job file name. If there is error information in place already when saving a new error it can be overwritten. Any corresponding uploaded files should be left in place.

erth9960 referenced this issue from DMC/play-api

2021-10-26 10:11:55 +02:00

Expose queue stats #2

erth9960 changed title from ~~Move failed jobs to separate directory~~ to Log failed jobs in separate directory

2021-10-26 10:28:58 +02:00

dafo5502 self-assigned this 2021-10-26 11:17:19 +02:00

dafo5502 added a new dependency 2021-10-26 11:19:01 +02:00

#6 Fixes #5

dafo5502 referenced a pull request that will close this issue

2021-10-26 11:19:23 +02:00

Fixes #5 #6

dafo5502 closed this issue