Summary
Right now, Heartbeat is unable to identify when a small change has occurred in an existing monitor config and so it adds it as a new monitor and removes the old versions. This has the side-effect of immediately triggering the execution which for regularly modified policies is not feasible.
It should be possible to implement a policy refresh function that detects when a monitor already exists in the scheduler a performs a background update of the config.
Summary
Right now, Heartbeat is unable to identify when a small change has occurred in an existing monitor config and so it adds it as a new monitor and removes the old versions. This has the side-effect of immediately triggering the execution which for regularly modified policies is not feasible.
It should be possible to implement a policy refresh function that detects when a monitor already exists in the scheduler a performs a background update of the config.