if you implement a accepted share count, and a rejected share count like other miners, it's easier to see wich of the workers that's just been restarted. Easier to troubleshoot
It's there, it's accessible via json-rpc or webui.
How do you monitor your workers? For large worker counts people usually use json-rpc.
Json-rpc will contain uptime and connection-time in the next release which is useful in this kind of situations.
If it's useful I'll output a/r shares also on terminal.
When a worker is restarted I loose hashrate.
Not sure if I understand this correctly. Do the GPUs perform slower after a restart?
