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

    You are viewing an old version of this page. View the current version.

    Compare with Current View Page History

    Version 6 Next »

    On this page:


    Related pages:

    Your Rating:
    1 Star2 Star3 Star4 Star5 Star
    5 rates

    Standalone Machine Agent Settings for Docker Visibility

    You can configure the following Docker Visibility settings on the Standalone Machine Agent.




    The Machine Agent can monitor up to 120 running containers (depending on the pool size configuration, described below) and does not prioritize. The agent collects metrics from containers that run with a configurable regex. By default, this regex matches processes that are are running with the -Dappdynamics prefix option. If you cannot restart the APM agents, or if you to want to filter APM agents based on another command-line argument, you can override this behavior by editing this regex.

    Default = ".*[ ]-Dappdynamics.*"

    You can configure this option in the following file: <machine-agent-home>/extensions/DockerMonitoring/conf/DockerMonitoring.yml

    Before you edit this file, please review "Editing YML Files: Important Notes" in Machine Agent Settings for Server Visibility.

    Docker Metric Collector Pool Size

    The Standalone Machine Agent can monitor up to 15 containers by default. You can configure the agent to monitor up to 120 containers at the same time: set the pool size to 5 (the default setting is 3). The trade-off is that increasing the pool size will consume more resources on the agent host. 
    To change the pool size, set the following. You cannot change this setting in the DockerMonitoring.yml file.

    • System Property - appdynamics.docker.metric.collector.pool.size

    Controller Settings for Docker Visibility

    sim.docker.enabledEnable the Docker Monitoring feature.true
    sim.docker.machine.container.limitGlobal limit for the number of containers to monitor per machine. You can specify this in the Administration Console as a Controller setting (all accounts) or as an Account setting for individual accounts. 120 is the maximum limit you can specify.15

    Reuse SIM Machine entities to handle ephemeral environment. Support is limited to docker container machines for now.

    If set to false, every new container will be considered a new machine.

    sim.docker.apmNode.markHistorical.enabledMark the APM nodes as historical when a container running an app agent is stopped.true
    • No labels