AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    Related pages:

    Your Rating:
    Results:
    1 Star2 Star3 Star4 Star5 Star
    27 rates

    This page describes Controller Admin settings that are specific to the Standalone 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. Consider the amount of Machine Agent data to retain when tuning the size of the Controller database.

    Change the Controller Settings for Standalone Machine Agents

    1. Log in to the Controller administration console using the root user password. See Access the Administration Console.

      http://<controller host>:<port>/controller/admin.jsp

      Use the root user password to access the Admin console when the Controller is installed in single- or multi-tenant mode. See User Management

    2. Select Controller Settings.
    3. Change the settings as needed, and then select Save
      Changes to the settings occur the next time you restart the Agent and it connects to the Controller. 

    Controller Settings Reference for Standalone Machine Agent 

    Property NameProperty DescriptionDefaultAllowed Values
    machine.agent.in-progress.actions.timeoutThis property determines the length of time 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.minMaximum 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 greater than the preset value, then the action is executed the next minute. 15 per minute1 to 28999999
    machine.agent.pending.actions.timeoutDetermines 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.sizeSize in Megabytes of the in-memory buffer storing machine snapshots uploaded from Agents prior to database flush.50 MB
    machine.snapshots.retention.periodTime in hours to retain server snapshot data.336 hours (2 weeks)1 to 840 hours (5 weeks)