[Feature Request]: Log when thermal runaway triggered

[evie-lau]

Is your feature request related to a problem? Please describe.
I was test-printing at a higher temperature and Octoprint kept disconnecting. Even when checking the logs, all I saw was that the connection was closed. I later realized it was the thermal runaway setting that triggered the connection closing.

Describe the solution you'd like
It would be helpful to have the plugin log that the thermal runaway temperature was reached, and is stopping the print.

Additional context
my serial.log:

2021-08-23 14:58:58,004 - Recv: ok
2021-08-23 14:58:58,008 - Send: N1205 G1 X93.869 Y93.177 E0.00995*87
2021-08-23 14:58:58,011 - Recv: ok
2021-08-23 14:58:58,030 - Send: N1206 G2 X94.912 Y93.870 I1.981 J-1.850 E0.04273*119
2021-08-23 14:58:58,034 - Recv: ok
2021-08-23 14:58:58,038 - Send: N1207 G1 X96.286 Y94.245 E0.04821*84
2021-08-23 14:58:58,050 - Connection closed, closing down monitor
2021-08-23 14:58:58,078 - Changing monitoring state from "Printing" to "Offline"

octoprint.log shows a similar story, just normal printing debug logs, and suddenly:
octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Offline"

Another thing I noticed, possibly a bug: even when the thermal runaway shutdown triggered, the print only paused, and did not move the print head or cooldown the nozzle/bed.

Edit: For more context, I don't actually use a smart plug on the printer.
So it just disconnected Octoprint, while my printer stayed on and seemed to freeze.

[jneilliii]

Because I keep my own log separate from octoprint.log I wouldn't be able to go that so easily. If debug logging is enabled in the plugin that information will be logged in the plugins debug log file in the logging section of OctoPrint. But adding a pop-up to the UI would be something that would be possible, but I would have to account for the situation where the UI wasn't already opened. I'll have to think on this one for a bit.