Title: Provide Webhook Logs / Logfiles
- What is your original issue/pain point you want to solve?
I want to be able to track problems in webhooks in order to be able to fix them.
- Which are one or two concrete situations where this problem hurts the most?
The webhook log in the web interface is very limited in quantity. The problematic webhook log line in the may have already been overwritten by newer webhooks when trying to track it.
- Why is it not solvable with the Zammad standard?
Zammad does not write this information to a log file and only has a very volatile display memory.
- What is your expectation/what do you want to achieve?
There are several possibilities.
The simplest would probably be to write the logs to a log file, similar to production.log.
Alternatively, a history could of course remain in the web interface, but this would probably have too great an impact on performance.
Only the latest logs are ever visible in the web interface. If you only have one webhook that is called up irregularly, this information is useful. However, if you have several webhooks or even just one that is called up relatively frequently, you may only have a history of a few minutes, if at all.