Heartbeat Monitoring items default template is the initiative after the windows mounted directly on the client, if uncoordinated time, there may be abnormal heartbeat data,
because it is a proactive monitoring, data on the active agent pushed to the server on, but the latest data from the server point of view, is intermittent, sometimes up to 5m, cause the trigger to fire, an alarm occurs (interval 30s). From the server log can see xxxx host connected restored, several clients have the latest data acquisition time lead or lag
Later restart the agent, also synchronize the data acquisition, data refresh is also normal