From @luiztauffer on slack: maybe we could improve the message here, to indicate that the compute resource is up and running. another idea would be to have some heartbeat health check, every minute maybe, to confirm that the service is up and running... but I'm not sure if that wouldn't pollute too much the logs.
Regarding the health check... the compute resource can check in periodically, but I don't think that this should be reported to the console... only report when something has gone wrong.
From @luiztauffer on slack: maybe we could improve the message here, to indicate that the compute resource is up and running. another idea would be to have some heartbeat health check, every minute maybe, to confirm that the service is up and running... but I'm not sure if that wouldn't pollute too much the logs.
Regarding the health check... the compute resource can check in periodically, but I don't think that this should be reported to the console... only report when something has gone wrong.