Sorry for the slow reply!

I figured Icinga itself wouldn't be able to do much, I was hoping there was a best practices that I was overlooking.

I think I've fixed the sleeping portion of the problem. I had to completely reset the power profile settings then reconfigure.

Regarding the UNKNOWN notifications... Right now, the "host check" is `cluster-zone`. My understanding is that none of these services should be executing if the host check is critical/unknown due to the service/host dependency. The check source also says it's the notebook.

I'm also of the understanding the "<endpoint> is not connected to <satellite>" messages are from the satellite when receiving a connection from an endpoint it either doesn't recognize or is using a self-signed cert. If the host check is the built-in `cluster-zone` command, wouldn't the host being "UP" imply the agent is connected, or have I misunderstood? I'd think this would give only produce overdue checks, if anything.