After installing some new software (not related to Pulseway) a reboot was required. As it happens, the server went down and no notifications were sent out. Looking at the Pulseway manager it looked like it was monitoring the server, however i got NO notifications about the downed server. When i ran a service pulseway restart... i quickly got a notification that the server was on-line. That seemed to resolve the problem.
My question is why does Pulseway not automatically do a restart when the machine is rebooted? Is this something i need to do every time a server is rebooted? I use Jenkins when i need to run mass jobs on our servers. Should i create a job that restarts the Pulseway service daily to avoid this from happening again? The only downfall with that is i don't want daily notifications that the server us up and running like it would send with the restart.
After installing some new software (not related to Pulseway) a reboot was required. As it happens, the server went down and no notifications were sent out. Looking at the Pulseway manager it looked like it was monitoring the server, however i got NO notifications about the downed server. When i ran a service pulseway restart... i quickly got a notification that the server was on-line. That seemed to resolve the problem.
My question is why does Pulseway not automatically do a restart when the machine is rebooted? Is this something i need to do every time a server is rebooted? I use Jenkins when i need to run mass jobs on our servers. Should i create a job that restarts the Pulseway service daily to avoid this from happening again? The only downfall with that is i don't want daily notifications that the server us up and running like it would send with the restart.
Any thoughts would be greatly appreciated.