log `Killed`: add reason
V
Vandeputte Brice
I am revising an image on one of my NodeJS applications. The application is killed during this treatment. Even when trying to break up the treatment with breaks.
If OnRender kills the application due to excessive resource usage (cpu/memory/i/o/bandwidth) or other reason (free plan, etc.) then it would be very pleasant for the user to understand what limit has been exceeded.
As a bonus: if the reason is added, then it would be even better to have a link to a help to understand how to address the problem (link to the doc and the limits, links to workarounds (e.g. rate limit), link to the paid plans)
(retro link: https://github.com/boly38/botEnSky/issues/110)
Log In
V
Vandeputte Brice
Oh mea culpa, on the mailbox corresponding to the application there is information that indicates which application was restarted and why (“Web Service xxx exceeded its memory limit”). So this point could be closed directly if it is not considered useful/simple to add a note directly into the logs (in addition).