Adjusting the timestamp
To disable this feature for all agents
Configure the following in services.cfg:
[Agent_Manager]
adjust_timestamp_attributes_by_skew=off
To enable this feature for all agents in a release that supports this feature (7.0.0.150 fixpack 1 or later)
To enable this feature for specific agents
and set the Adjust_Timestamp_Attributes_By_Skew agent preference using agentpref to on or off.
agentpref --set-agent Adjust_Timestamp_Attributes_By_Skew on
or
agentpref --set-agent Adjust_Timestamp_Attributes_By_Skew off
The following additional services.cfg keywords might be necessary to adjust the samples used to calculate the average skew.
skew_logic_samples_to_calculate_avg – this value defaults to 5. It defines the number of samples used to calculate the skew average. Acceptable values are 1-10. The smaller the number of samples the more reactive the service might be to time changes but accuracy/consistency across longer transactions is lost.
skew_logic_min_thresh_ms – this value defaults to 1000 milliseconds. The skew should not include any delays internal to the agent. This value defines the minimum the amount of time the agent must be sitting in a select waiting for socket activity before the skew adjustment is considered accurate. In very active agents a higher threshold might result in the skew never being calculated. In this case it could be reduced. It is not recommended this value be changed.