- Machine Agent Settings for Docker Visibility
- Controller Settings for Docker Visibility
Machine Agent Settings for Docker Visibility
You can configure the Docker Visibility settings 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.
|The Machine Agent can monitor up to 150 running containers (depending on the pool size configuration, described below). The agent collects metrics from containers with one or more running processes whose command line matches a configurable regex. By default, the value of this regex is ".*|
Default = ".*"
Docker Metric Collector Pool Size
Specifies the local limit for the number of containers the agent can monitor. The effective limit for each agent is the minimum of
You can change this setting to monitor up to 120 containers (pool size = 4) or 150 containers (pool size = 5). The trade-off is that increasing the pool size might lead to higher resource consumption on the agent host.
To change the pool size, set the following.
Enable (the default) or disable the collection of Docker tags from containers monitored by this agent.
The Standalone Machine Agent can collect Memory and CPU metrics for Docker containers using cgroupdata. This method is much faster than using the Docker API (the default metric-collection method). You can enable cgroupmetriccollection on all platforms except Amazon Linux OS. With the cgroup enabled flag set to
This mode is disabled by default. To enable cgroupmetriccollection, run the agent with the following command-line option set to true:
java -Dappdynamics.docker.container.collection.cgroup.enabled=true -jar machineagent.jar
Controller Settings for Docker Visibility
For information about how to configure these settings, see Controller Settings for Standalone Machine Agents.
|Enable the Docker Monitoring feature.||true|
Global limit for the number of containers that each agent can monitor. The effective limit for each agent is the minimum of
You can specify this in the Administration Console as a Controller setting (all accounts) or as an Account setting for individual accounts. 150 is the maximum limit you can specify.
Reuse SIM Machine entities to handle the ephemeral environment. Support is limited to Docker container machines for now.
If set to false, every new container will be considered a new machine.
|Mark the APM nodes as historical when a container running an app agent is stopped.||true|
|Enable or disable the import of Docker tags to the Controller.||true|