Project

General

Profile

Actions

User story #5576

closed

User story #5293: Add a 'changes only' compliance mode, only reporting changes on systems

Add a heartbeat feature that force agent to periodically contact Rudder

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

Status:
Released
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

With the changes only mode defined in #5293, we can imagine having nodes NEVER contacting Rudder because everything is in success.

From a use point of view, we need to have periodically some kind of "hey, I'm alive!" message, allowing to know that nobody actually shutted down the server.

There is 3 main parts on that feature:

- some UI bits allowing to configure how frequently a node send a heartbeat;
- some Rudder backend work to store that information by node and have the necessary plumbing to give the information to the corresponding node;
- on the node, the logic in techniques to understand and act accordingly to the configured heartbeat frequency.


Subtasks 6 (0 open6 closed)

User story #5577: UI for configuring heartbeat by nodeReleasedFrançois ARMAND2014-09-26Actions
User story #5578: Heartbeat Rudder/technique integrationReleasedFrançois ARMAND2014-09-26Actions
User story #5579: Send reports from the agent to provide a heartbeatReleasedNicolas CHARLES2014-11-29Actions
Bug #5874: Start message from system techniques is sometimes not printed due to over-zealous lockingReleasedNicolas CHARLES2014-11-29Actions
Bug #5878: Apply fix from #5874 to ncf's copyReleasedNicolas CHARLES2014-11-29Actions
Bug #5883: Missing system variables for RUDDER_HEARTBEAT_INTERVAL and SEND_METRICS in TechniquesReleasedNicolas CHARLES2014-11-29Actions

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #5837: Eventlogs to track global hearbeat change is missingReleasedFrançois ARMAND2014-12-12Actions
Actions #1

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 140 to 3.0.0~beta1
Actions #2

Updated by Jonathan CLARKE about 10 years ago

  • Status changed from 8 to 12
Actions #3

Updated by Jonathan CLARKE about 10 years ago

  • Status changed from 12 to Pending release
Actions #4

Updated by Vincent MEMBRÉ about 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.

Actions

Also available in: Atom PDF