Scenario: Heartbeat interval for agent class

Learn how you can control the the heartbeat interval at the agent class level and resolve related issues.

Scenario: You have an agent class with agents deployed in a new department where all the hardware and network performance exceed the rest of the system and heartbeat is configured to 5 seconds for those agents.
Analysis: You can configure the maximum heartbeat interval at the class level using the following parameter: efm.monitor.maxHeartbeatIntervalForClass.[ClassA]=10s

The following chart shows how Edge Flow Manager considers an agent healthy based on these settings:

important
Increasing the value of the maxHeartbeatIntervalForClass parameter, allows more time for agents in a specific class. However, too many unhealthy agents in this class would slow down bulk operations significantly.
Solution: You can introduce stricter expectations by setting efm.monitor.maxHeartbeatIntervalForClass.[ClassA]=6s. With inQueuedStateTimeoutHeartbeatRate=8, the Edge Flow Manager waits only 48 seconds before timing out an operation and notifying you about the issue.