You can increase or decrease the default metric registration limits for machine agents or app agents.

Changing these limits can affect the resource consumption of your deployment. Before you change this setting verify your application environment and Controller can handle the increased resource requirements.

For the Java agent, modify the limit using the agent.maxMetrics system property. For example, to increase the machine agent metric limit, specify the maximum number of metrics as an argument when starting the machine agent in the following format:

-Dappdynamics.agent.maxMetrics=<max-number-of-metrics>

For example, when starting the machine agent, increase the maximum number of metrics that can be registered to 2000 as follows:

nohup java -Dappdynamics.agent.maxMetrics=2000 -jar machineagent.jar &

For the .NET Agent, set the maxMetrics property as an environment variable. This setting only affects the app agent. For example:

appdynamics.agent.maxMetrics=5500

For the .NET Agent for Linux, use the node property below to set agent metric limits. See App Agent Node Properties (A) for more information.

appdynamics.agent.metricLimits

For the .NET Machine Agent, specify the maximum number of metrics using the Metrics element in the config.xml. See 'Machine Agent Element' on .NET Agent Configuration Properties. See also Administer the .NET Agent.

<metrics max-metrics="300"/>