Related pages:

Configuration templates enable you to define a set of default configuration values that apply across a set of rulebooks. The configuration templates are stored on the AppDynamics Controller and used to update the rulebooks on machines where the Universal Agent manages the runtime agents. The use of configuration templates is optional, however, using them can reduce the size of your rulebooks and simplify rulebook management across a set of machines. 

Background

The rulebook for each Universal Agent instance uses a JSON object called config to define a set of key-value pairs containing configuration values that are specific for the agent that is being monitored.  These config objects can be large and in many cases may contain redundant fields across numerous runtime agents that are being managed by a single Universal Agent instance.

Configuration templates implement a JSON object that defines a basic, default configuration for your runtime agents. The template object is a set of key-value pairs that can be referenced in your rulebooks at both the header level (applying globally to all runtime agents in the rulebook) and in agent-specific rules.

The configuration template is applied to the rulebook first, and properties in the config object in the rulebooks can override the default values if needed for specific use cases.

Users with the Configure Universal Agent permission can create and update configuration templates using the REST APIs.

  • Configuration templates can be used only when running the Universal Agent in controller mode.
  • The rulebooks reference applicable configuration templates using the configEntity property. 
  • Individual rules in your rulebook can override values defined in the templates using the rule-level config object.
  • When the Universal Agent processes a rule that contains a configEntity property, a request is sent to the Controller for the content of the specified template. The template values are then pushed to the Universal Agent, where they are applied to the rulebook. 
  • The Universal Agent reports the version ID of each rulebook and template that was sent in the prior cycle back to its Controller. If necessary, the Controller then sends more recent versions of the rulebooks and templates back to the Universal Agent.