Compliance reporting mode
This setting affects the reports sent from each agent to this central server.
  • In Full compliance mode, a report will be sent for each configuration component that is checked, even if no changes were necessary (these are known as 'success' reports). This mode is much more verbose, in terms of logs and network traffic, but provides more precise reporting and may be necessary to prove compliance in your organization.
  • In Non compliant only mode, reports will only be sent when the agent makes a change or an error occurs on a node (these are 'repair' or 'error' reports). This mode saves a lot of log space and bandwidth, but leads to some assumptions about actual configuration status in reporting.
  • In Disabled mode, no reports will be sent, and rudder-agent will not re-configure the local syslog to send reports. This mode uses no log space or bandwidth, but will also not allow you to check if your configuration policy is successfully applied. We do not recommend using this mode except for setups where you have another feedback mechanism in place.
Agent run heartbeat
In "changes only" compliance mode, the agent will, by default, report a "heartbeat" every time it runs.
A heartbeat is a set of two reports (startRun/endRun). When no other events are reported (no errors and no repairs), this is the only feedback sent by the node.
The bandwidth consumed by these messages is tiny, but can add up over time. The setting below allows to change the frequency of the heartbeat message, so that it is only sent every N runs.
In "changes only" compliance mode, the agent will report a "heartbeat" when no other events are reported (no errors and no repairs). This frequency can be changed to send a heartbeat only every N runs.
This setting is defined as a default for all nodes in the global Settings.
The current global setting is to run every {{globalValue.heartbeatPeriod}} runs, (so every {{globalValue.heartbeatPeriod * agentRun}} minutes).
You may override this global setting just for this node below:
Heartbeat will be sent every {{complianceMode.heartbeatPeriod * agentRun}} minutes
Number of runs between heartbeats cannot be empty Number of runs between heartbeats must be a valid integer Number of runs between heartbeats must be in range from 1 to {{checkMaximumValue()}} (24 hours with a {{agentRun}} minutes frequency)
[messages]