I wanted to clear my concept of infrastructure monitoring. Today, I noticed that one of the servers went offline at 10:30 AM and came back at 10:54 AM.
In the hosts' dashboard, one was grayed-out and other was active.
The downtime/offline time was 24 minutes but we can see that the offline time of the unavailable host keeps increasing even though the server is available.
Also, there is no connectivity on the graph between offline and uptime with the unavailable time.
Solved! Go to Solution.
If you have new host not old one back active this means that agent was reinstalled all even host recreated. We have the same issue with AWS deployments where hosts are destroyed and started again. Right now there is no option for linking them for continuous data set.
Data are missing because during blank there was no monitoring at all.
Hello @sebastian k.
🙂 thank you for pointing me to the right location.
I can see that both hosts (offline and online) have different IDs. So can I assume that this was a restoration of the VM instead of a restart?
I was posting RFE for ability to manual define such host ID during installation of agent for such purposes but for now, no response.
I just want to add on to what Sebastian has mentioned. Usually if it's a static host, then upon uninstallation of the agent, there would still be some static remnants left behind; these are used when we reinstall the agent, and the agent will recognize that this was previously monitored so data continuity will be maintained. It's a totally different story if it's cloud deployment where hosts can be destroyed and "respawn" as completely new host.
Hello @Christopher C.
Thank you for your comments. We have a managed setup with a lot of virtualized setup. If system administrators restore the VM at any stage then there will be two different host IDs as we discovered in the current issue.