Alerting Disconnect edge case
alexandreLamarre opened this issue · comments
We currently cannot track the case when the health api on startup fails and the agent is disconnected. This will be the case in the next release when v0.10 agents receive a config that cannot be loaded from the gateway.
On startup, we should retry a limited amount of times to read the health api, and if there are no successes publish a connected = False method to the disconnect message stream.