Logging to detect unhealthy agents on agent side

We’ve found a number of agents that are in an unhealthy (not checking in) state. Some are just temporarily hung and need a service restart. Some require a reinstall because they were accidentally/agressively cleaned out from ImmyBot. We’d typically account for such scenarios by scheduling a task on the agent side that checks for unhealthy conditions in the agent and responds accordingly. Unfortunately, according to our own research and responses from ImmyBot support, we’re not able to detect if the agent is healthy or not from the agent side as the log output of a “bad” agent is essentially identical to the log output of a “good” agent.

Given that we rely on ImmyBot to install/update software that is critical to our clients’ security it’s highly important that we make sure ImmyBot is functioning at all times.

Thanks and happy holidays,

Being able to auto-heal immybot agents after detecting they’re unhealthy could be a really solid safety net to be sure that we’re not relying on an agent that isn’t actually able to run maintenance.

I’ve had success with restarting the immybot service on a system in question through ScreenConnect, so having a way to leverage control to restart the service or maybe another method to auto-heal this issue could be a useful advantage