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

« Previous Version 36 Next »

On this page:

 

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
1 rates

Standalone Machine Agent Settings for Docker Visibility

You can configure the following Docker Visibility settings on the Standalone Machine Agent. See also Standalone Machine Agent Configuration Property Reference.

 

Setting
Description

containerProcessSelectorRegex

The Machine Agent can monitor up to 150 running containers (depending on the pool size configuration, described below) and does not prioritize. The agent collects metrics from containers with one or more running processes whose command line matches 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

Specifies the local limit for the number of containers the agent can monitor. The effective limit for each agent is the minimum of

  • The sim.docker.machine.container.limit on the Controller (default limit = 15 containers), or
  • The Docker Metric Collector Pool Size on the agent (default pool size = 3, or 90 containers).

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. You cannot change this setting in the DockerMonitoring.yml file.

  • System Property - appdynamics.docker.metric.collector.pool.size
  • Environment Variable - APPDYNAMICS_DOCKER_METRIC_COLLECTOR_POOL_SIZE

dockerTagsEnabled

Enable (the default) or disable the collection of Docker tags from containers monitored by this agent.

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

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

cgroup Enabled

The Standalone Machine Agent can collect Memory and CPU metrics for Docker containers using cgroup data. This method is much faster than using the Docker API (the default metric-collection method). You can enable cgroup metric collection on all platforms except Amazon Linux OS.

This mode is disabled by default. To enable cgroup metric collection, 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.

Property
Description
Default

sim.docker.enabled

Enable the Docker Monitoring feature.true

sim.docker.machine.container.limit

Global limit for the number of containers that each agent can monitor. The effective limit for each agent is the minimum of

  • The sim.docker.machine.container.limit on the Controller (default limit = 15 containers), or
  • The Docker Metric Collector Pool Size on the agent (default pool size = 3, or 90 containers).

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.

15

sim.machines.reuse.enabled

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.

true

sim.docker.apmNode.markHistorical.enabled

Mark the APM nodes as historical when a container running an app agent is stopped.true

sim.machines.tags.enabled

Enable or disable the import of Docker tags to the Controller.true

 

 


  • No labels