Within the "Server Management" page of the Kronos dashboard, a table called "Node-reboots" is present.
This table indicate any logged entries for reboots done within Kronos, the following types of reboots are possible
Manual reboots, are any reboot caused by the admin or the user by clicking the "reboot node" button
Uptime Robot reboots, are executed by Kronos, when Uptime Robot is enabled, and a node is detected as being down, Kronos will attempt to reboot the node
This only works for Hetzner servers, with the Hetzner API configured within Kronos
These are caused by appbox customers - When a customer reboots an appbox, Kronos will execute a check shortly after the reboot, to see if the docker container successfully rebooted, if it did not, Kronos will fire a soft reboot to the node.
If the soft reboot fails, and IF the node is a Hetzner node AND the Hetzner API is configured, Kronos will fire a forced reboot via the hetzner API.
Kronos will fire up to 3 forced reboots, with 2 minute intervals - If the node is still not back, Kronos will submit a manual reboot request to Hetzner via the Hetzner API