GIM dynamic updating

GIM clients check for updates from the GIM server at regular intervals. The GIM server can calculate the best polling interval to use based on system conditions.

Each GIM client sends an alive message to its GIM server regularly, to check whether any updates are ready to be processed. This polling interval is calculated and updated based on conditions at the GIM server. The interval is calculated regularly, and the new value is passed to the GIM client in response to its alive message. This feature is enabled by default, but you can turn it off if you prefer a fixed interval.

Dynamic updating is controlled by the Guardium API command gim_set_global_param, with these parameters.
dynamic_alive_enabled
Dynamic alive feature control. 1 – enabled, 0 – disabled. Default =1
dynamic_alive_check_interval
The interval, in minutes, at which the polling interval is recalculated. Default = 5
For example:
grdapi gim_set_global_param dynamic_alive_enabled=0

When each GIM client sends its alive message to the server, the server responds with the new polling interval as well as any other updates that have been scheduled for that client.

These parameters were valid in 10.0, and removed from 10.1 and higher:
  • dynamic_alive_default_load_factor
  • dynamic_alive_cpu_level1_threshold
  • dynamic_alive_cpu_level2_threshold
  • dynamic_alive_db_conn_level1_threshold
  • dynamic_alive_db_conn_level2_threshold
  • dynamic_alive_cpu_load_sample_time