Open evilsizorm opened 4 years ago
A debug log would be really great.
We have often problems, where it is hard to say where they were caused (daemon, server, local printer, ...).
@evilsizorm, please give the latest beta a try, if you like: https://github.com/ExLibrisGroup/alma-print-daemon/releases/tag/v2.2.0-beta-02
Hi mgobat, we recently implemented Alma Print Daemon 2.2.0 and have taken a look at the new loggings. Would it be possible to add the Alma Request-IDs to the loggings? I'm asking because we experience delayed processing of requests to the printers and are looking for the cause.
Hi @Stegewans. Unfortunately, the request id isn't available in the API response to retrieve the printouts for printing. This will require an update to the API itself first.
Hi mgobat, thanks for the info; what will it take to update the API for this? Can I do anything? Regard, Lammert
Hi @Stegewans. API updates have to go through the standard Alma enhancement process. Could you provide more details about the issue you are having with delayed processing of requests? Do you have an iQuest case open with Support? Thanks.
It would be a very nice enhancement if a log file could be created. This would help us track down an Alma Printouts Queue that is marked as printed, but we are uncertain if it reached our printer or not.
Perhaps 7 rolling simple text files that note the date, time, Alma Printouts Queue Source and Printout column values. On the eighth day it would clear file 1 and start logging to it again.
Thanks, Mark