This topic describes Controller Admin settings that are specific to the Machine Agent. You need the root user password to change these settings.
You can change the amount of Machine Agent data you retain in the Controller database by changing the retention period for machine agent snapshots. Lowering the retention settings purges data that is aged out by the new retention setting and reduces the amount of data stored by the Controller on an ongoing basis. When tuning the size of the Controller database, this can be a good place to start.
To Change the Controller Settings for Machine Agents
Use the root user password to access the Admin console when the Controller is installed in single- or multi-tenant mode. For a discussion of the root password, see User Management.
Click Controller Settings.
Change the settings as needed and Save. Changes to the settings take effect the next time the agent is restarted and connects to the Controller.
Controller Settings Reference for Machine Agent
Property Name
About the property
Default
Allowed Values
machine.agent.in-progress.actions.timeout
This property determines how long the Controller waits for the agent to perform an IN-PROGRESS action before it stops the action.
86400000 ms
(1 day)
1 to 840 hours (5 weeks)
machine.agent.max.new.actions.per.min
Maximum number of new actions dispatched per minute for each machine agent. This is the maximum number of "runbook" actions sent to the machine agent. For example, you may request the machine agent to run a script because of a health rule violation, if the number of requests in a one minute period is more than the preset value, the action is executed the next minute.
15 per minute
1 to 28999999
machine.agent.pending.actions.timeout
Determines how long the Controller waits for the agent to perform a PENDING action before it stops the action.
1800000 ms
(12 hrs)
machine.agent.snapshots.buffer.size
Size in Megabytes of the in-memory buffer storing machine snapshots uploaded from agents prior to database flush