KNOWN ISSUE: Erroneous Heartbeat alerts triggering
Last Updated March 29, 2012
Heartbeat alerts are occurring for machines which are online and the Monitor Agent is running. These alerts are then resolved shortly after occurring.
While there is a server-side retry mechanism for checking Heartbeats, there is no agent-side mechanism to ensure the Heartbeat was sent in time. If a Heartbeat fails to make it to the server for any reason, the polling interval will reset and the next Heartbeat may not be sent to the server in time causing a Heartbeat alert to occur.
This is a known issue. It is under investigation and will be resolved in future release.
A possible workaround may be to adjust the Heartbeat settings to compensate for this:
Access the Data Collection tab for each Monitor Agent configuration policy
Change the Send heartbeat every: value to "10 Minutes", then Save Changes
Access the Heartbeat tab in the Monitor Server Settings configuration policy
Change the values to Check for heartbeat every: "12 Minutes", Retry every: "230 Seconds", and Retry attempts: "3"
This will allow for a period of 2 missed Heartbeat alerts to occur before a Heartbeat alert is triggered.
Monitor Solution for Servers 7.x
ID: ETK 1928319
Logged in Etrack (Symantec) database
Imported Document ID: TECH121854
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe