Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a crash log #6392

Open
matthias-ronge opened this issue Jan 30, 2025 · 1 comment
Open

Implement a crash log #6392

matthias-ronge opened this issue Jan 30, 2025 · 1 comment
Labels

Comments

@matthias-ronge
Copy link
Collaborator

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.

@henning-gerhardt
Copy link
Collaborator

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" / ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants