BigFix clients report to server in every 15 minutes by default.
My first question is:
“how often does BigFix Client evaluate the all its contents in this report period ? Once per report ? or more ?”
Second is
"what if the evaluation cycle exceeds the report period (15 Minutes) ?" does it wait to complete the all evaluation ? or does it send the report with latest values to the server ?
First answer, the client will report (depending on your minimum reporting interval) whenever anything changes. The heartbeat value merely says “when you reach the end of the content loop report anyway even if there has been nothing changed”
Second answer, note the way I answered the first question, you need to reach the end of the content loop so if the evaluation cycle exceeds the heartbeat you will report on the end of the evaluation cycle after the heartbeat has been reached.
I understand that, during one report cycle (15 Minutes), the client can evaluate the same fixlet more than once.
if I create a policy action which is set to run whenever it becomes relevant (without waiting), the duration of “becoming relevant” depends on the content loop’s end. not depends on heartbeat cycle. am I right ?
why do we increase the client’s heartbeat interval ? for server’s performance or for client’s performance ?
Correct, the duration of ‘becoming relevant’ in the case above depends on the Client’s evaluation loop, and not the heartbeat.
Increasing the heartbeat interval can be useful for both Server performance (reduce the amount of incoming data), as well as Client performance (in general, you want the heartbeat interval to be longer than the evaluation loop for most Clients to avoid missing heartbeats).