Download page Configure Docker Visibility.
Configure Docker Visibility
Machine Agent Settings for Docker Visibility
You can configure the Docker Visibility settings in the file:
Before you edit this file, please review "Editing YML Files: Important Notes" in Machine Agent Settings for Server Visibility.
The Machine Agent can collect Memory and CPU metrics for Docker containers using
This mode is disabled by default. To enable
|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 = "
Specify the local limit for the number of containers the agent can monitor. The effective limit for each agent is the minimum amount for:
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 these properties:
default limit = 15 containers
default pool size = 3, or 90 containers
|Enable (default) or disable the collection of Docker tags from containers monitored by the Machine Agent.|
Use the Machine Agent to identify containers by container names only.
By default for Docker monitoring, the Machine Agent obtains a list of containers. For each container, the Machine Agent retrieves all running processes inside the container. Then, the Machine Agent matches the container to be monitored by the process full command line. Because there are many containers, the selection process lasts longer than a minute, causing gaps in reporting container metrics.
The Docker Use Container Name Selector configuration option provides an alternative way to select containers to be monitored by using the container's name. This option allows the Machine Agent to run significantly faster since the Machine Agent does not have to gather all the processes for each container.
To enable matching with the container name, you can either use an environment variable or a JVM property. If both are defined, the environment variable is used.
To exclude containers from monitoring, use an environment variable or the JVM property. If both are defined, the environment variable is used.
# default value ".*(machine-agent|machineagent).*"
Controller Settings for Docker Visibility
For information about how to configure these settings, see Controller Settings for Machine Agents.
|Enables configuration to mark the APM node historical when a container running the app agent is stopped.|
|Enable the Docker Monitoring feature.|
Global limit for the number of containers that each Machine Agent can monitor. The effective limit for each agent is a 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 an ephemeral environment. Support is currently limited to Docker container machines.
If set to
|Enable or disable the import of Docker tags to the Controller.|