PDFs

Skip to end of metadata
Go to start of metadata

On this page:

Related pages:

You can install, maintain, and run .NET Agents with the AppDynamics Universal Agent. The Universal Agent uses a rulebook to determine which versions of the .NET Agent should be installed and deployed. You need to define and configure the .NET Agent entry in the Universal Agent rulebook.

Define .NET Agent Rules

A monitor value of dotnet identifies a .NET Agent rule. 

The valid values for the state property for a .NET Agent rule are:

  • installed
  • started

.NET Agent Rule Syntax

.NET Rules
{  
   "condition":"platform_family == 'windows'",
   "comments":"...comments...",
   "name":"...name of rule...",
   "monitor":"dotnet",
   "config":{  
      "version":"....NET agent version...",
      "state":"installed | started",
      "controller_host":"...name of host running controller...",
      "controller_port":"...port number controller is listening on...",
      "account_name":"...controller account name...",
      "account_access_key":"controller account access key...",
      "controller_ssl_enabled":"true",
      "controller_tls12_enabled":"false",
      "controller_secure_enabled":"false",
      "config_xml":[  
         "list of repositories where a paired config.xml can be found"
      ]
   }
}

The following properties are defined for the Universal Agent and common to all agent types. The values have no special meaning for the .NET agent:

  • name: A string for quickly identifying the rule.
  • comments: A long string describing the rule's purpose.
  • monitor: Name of the targeting monitoring agent (for .NET Agent, must be "dotnet").
  • condition: The conditions for applying the rule. This consists of a Boolean expression where the operands are the values collected by the Environment Modules.
KeywordDescriptionExample
versionThe version of the .NET Agent to run."version": "4.4.0.0"
state

Indicates how the .NET Agent should deploy on the target machine.

  • "installed": downloads the specified version of the .NET Agent
  • "started": a version of the .NET Agent is installed and is active
"started"
controller_host

Identifies the name of the Controller host where the agent should connect. This property is optional in the rule; it can be inherited from the controller_host property defined in the header section of the rulebook or from the Controller identified in the universalagent.yaml file.

"localhost"
controller_port

Identifies the port number of the Controller where the agent should connect. This property is optional in the rule; it can be inherited from the controller_host property defined in the header section of the rulebook or from the Controller identified in the universalagent.yaml file.

"8080"
account_name

Identifies the account name that is passed to the Controller when the agent attempts to connect. This property is optional in the rule; it can be inherited from the controller_host property defined in the header section of the rulebook or from the Controller identified in the universalagent.yaml file.

"customer1"

account_access_key

Identifies the account access key that is passed to the Controller when the agent attempt to connect. This property is optional in the rule; it can be inherited from the controller_host property defined in the header section of the rulebook or from the Controller identified in the universalagent.yaml file.

"SJ5b2m7d1$354"

controller_ssl_enabled

SSL is enabled"true"

controller_enable_tls12

tls12 is enabled"false"
controller_secureSecure is enabled"false"
config_xml

Specifies, in JSON format, a list of repository URLs where config.xml, related scripts, and binaries are located.

See Configuring the .NET Agent.

[repository,repository,...] where repository=server URL, such as http://server/path or file://local/path

Example .NET Agent Rule

In this example, the controller and account settings are not shown because they are inherited from the global Universal Agent config or from the universalagent.yaml file.

Example of a .NET Agent Rule
{  
   "condition":"platform_family == 'windows'",
   "comments":"This is an .NET Agent rule",
   "name":".NET Agent rule for Windows",
   "monitor":"dotnet",
   "config":{  
      "state":"started",
      "version":"4.4.0.0",
      "config_xml":[  
         "file:///C:/Tools/Repo"
      ]
   }
}

Configuring the .NET Agent

The Universal Agent installs the .NET Agent and deploys the configuration file (config.xml) specified in the rulebook. The .NET Agent uses the config.xml file to determine which processes to instrument upon restart of the process. It is up to you to build the config.xml file and specify its location using the config_xml property in the .NET rule. A sample setup configuration file can be viewed in Unattended Installation for .NET

For each .NET Agent version, you can specify a corresponding config.xml. This config file is retrieved from the repository specified by config_xml. The location can be local to the machine in a shared directory, or external.

 

  • No labels