I'm having a frequent problem recently with my players. I currently have 20 players and on occasion, one of them will report a "Communication Error" and all testing will come to a stop.
Simply rebooting the player fixes the issue every time and is quick. Operations though will sometimes leave the player in this state for hours before contacting me...
Restarting the service will also fix the problem usually but some of these players are Amazon AWS nodes and with those, it's easier to just reboot them.
Is there anyway to just have Solarwinds reboot the player in question in these situations? Or, anyway to have the service monitor itself on the player and restart itself when this occurs?