You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A crashed automatic task can disappear from the task manager for various reasons: after a certain amount of time, by manually clicking delete, or when logging in again (the latter after hearing from a colleague, I have not yet seen the case). You can then no longer see why the task crashed. There should be a crash log. This could be added in the processes’ comments area. At the moment there is only the possibility to search in the kitodo.log.
The text was updated successfully, but these errors were encountered:
So far as I can see in our crashed tasks they are logged into kitodo.log and this file is monitored by our monitoring system. So we see all of the crashes and the reasons behind - depending on how the log is created - but in most cases we are know which task is crashed with which reason.
Adding the crash log to the comments area of a process is not a good solution as so a lot of non-IT colleagues would see this messages and did not know how to handle same. As only the issuer of a comment (and maybe other people with the right access rights) can delete only comments this comments may stay for a really long time.
An other point is: you must find this crash log comments in an easy way.
For admin users it would be better to see this crash logs not only in the kitodo.log file may even in a separate view in the application where may even notices could be added and / or deleted to every single crash log and the crash log itself can be adjusted to "solved" / "under investigation" / ...
A crashed automatic task can disappear from the task manager for various reasons: after a certain amount of time, by manually clicking delete, or when logging in again (the latter after hearing from a colleague, I have not yet seen the case). You can then no longer see why the task crashed. There should be a crash log. This could be added in the processes’ comments area. At the moment there is only the possibility to search in the
kitodo.log
.The text was updated successfully, but these errors were encountered: