User story #5576
closedUser story #5293: Add a 'changes only' compliance mode, only reporting changes on systems
Add a heartbeat feature that force agent to periodically contact Rudder
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.
Updated by Matthieu CERDA about 10 years ago
- Target version changed from 140 to 3.0.0~beta1
Updated by Jonathan CLARKE almost 10 years ago
- Status changed from 12 to Pending release
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/