Monitor etcd connectivity

Since the heartbeat provides presence information, a failed heartbeat means the fleet server is no longer able to operate in the cluster. The Heart and Monitor pieces are now responsible for the Machine heartbeat. The Monitor provides a trigger for stopping, purging, and starting the fleet server in response to a failed heartbeat.
I'd like to see some package/struct docs, since `Monitor`, `check`, etc are all rather ambiguous and overloaded terms