User story #5577
closed
User story #5293: Add a 'changes only' compliance mode, only reporting changes on systems
User story #5576: Add a heartbeat feature that force agent to periodically contact Rudder
UI for configuring heartbeat by node
Description
The UI that allows to configure heartbeat frequency by node.
The frequency really is configured for each node + one global default value, but we don't want a user to have to go to each nodes of a group to change their heartbeat frequency. So we need some kind of action in the group or search screen that allows to change that parameter.
Moreover, the frequency must be defined in term of multiples of the agent run frequency, else we will risk inconsistencies like having a heartbeat frequency all the 5 minutes when the agent actually run only one time by hour on the node (or with a less naïve example, agent period = 10 minutes, heartbeat = 45 minutes)
Updated by Jonathan CLARKE almost 10 years ago
- Category set to Web - Maintenance
- Status changed from New to 8
- Assignee set to Vincent MEMBRÉ
- Target version set to 3.0.0~beta1
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from 8 to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/665
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 27fbbefb54883b9032979794b0e149f108b10fab.
Updated by François ARMAND almost 10 years ago
Applied in changeset 2b7c3cd93a4803ebe194a6c206b650a28047740d.
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.
- Announcement
- Changelog
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE over 9 years ago
- Tracker changed from Enhancement to User story