User story #5577: UI for configuring heartbeat by node - Rudder - Issue Tracker

Actions

Copy link

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

Added by François ARMAND about 10 years ago. Updated over 9 years ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Web - Maintenance

Target version:

3.0.0~beta1

Pull Request:

https://github.com/Normation/rudder/p...

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

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)