This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.


Skip to end of metadata
Go to start of metadata

On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
51 rates

You can migrate the transaction detection configuration for all entry points from one application to another using the AppDynamics REST API. The API allows you to avoid having to manually reconfigure across multiple applications in the Controller.

Import and Export Auto-Detected Entry Point Configurations

You can import and export all your entry point configurations or one entry point configuration in a single request. You cannot import or export multiple entry points in a single request unless you import/export all of them.

You can import to or export from the following application-level and tier-level configurations:

  • Auto-detected entry point configurations

  • Custom match rules

  • Exclude rules

Guidelines for exporting entry point configurations:

  • Use the HTTP GET method.
  • Encode the URI using UTF-8 URL encoding.

  • The Controller exports the configurations to an XML file. If necessary, you can edit the XML file before you import it.
    For example, if you export all auto-detected entry points but don't want to import them all, delete the ones you do not want from the file before import.

Guidelines for importing entry point configurations:

  • Export the auto-detected entry point configuration, custom match rule, or exclude rule from the Controller.
    Alternately, you can manually create the XML.

  • Use the HTTP POST method.
  • Encode the URI using UTF-8 URL encoding.

  • Include the XML configuration as a file attachment to the request.

  • Use UTF-8 URL encoding of the URI before posting.

  • To overwrite an existing configuration with the same name see Overwrite Parameter.

  • A successful import request returns HTTP status code 200.

Import or export the configurations for all the auto-detected entry-points to or from an application

http://<controller host>:<controller port>/controller/transactiondetection/<application name>/auto

exports all the auto-detected entry point types for all agents: ASP.NET, Java, PHP, NodeJS, etc.

For example:

http://appdcontroller.example.com/controller/transactiondetection/Howdy+World+Travel/auto

produces the output in auto_all.xml.

Import or export the configuration for a single auto-detected entry point type to or from an application

http://<controller-host>:<controller-port>/controller/transactiondetection/<application name>/auto/<entry point type name>

The following entry point type names are valid for their respective agents. Entry point types names are case insensitive.

Java.NETPHPNode.js
binaryRemoting (for Thrift)
servlet
strutsAction
springBean
ejb
pojo
jms
webService

aspDotNet (for ASP.NET)
dotNetWebService (for Web Service)
wcf
poco (for .NET Class/Method)
dotNetJms (for Message Queues)
dotNetRemoting

phpWeb
phpMvc
phpDrupal
phpWordpress
phpCli
phpWebService

nodeJsWeb

Import or export the configurations for all the auto-detected entry-points to or from a tier

http://<controller-host>:<controller-port>/controller/transactiondetection/<application name>/<tier name>/auto

Import or export the configuration for a single auto-detected entry point type to or from a tier

http://<controller host>:<controller port>/controller/transactiondetection/<application name>/<tier name>/auto/<entry point type name>

Import and Export Custom Match Rules

Import or export a single custom match rule to or from an application

http://<controller host>:<controller port>/controller/transactiondetection/<application name>/custom/<entry point type name>/<custom rule name>

Import or export a single custom match rule to or from a tier

http://<controller host>:<controller port>/controller/transactiondetection/<application name>/<tier name>/custom/<entry point type name>/<custom rule name>

Import and Export Exclude Rules

Import or export a single exclude rule to or from an application

http://<controller host>:<controller port>/controller/transactiondetection/<application name>/exclude/<entry point type name>/<exclude rule name>

Import or export a single exclude rule to or from a tier

http://<controller host>:<controller port>/controller/transactiondetection/<application name>/<tier name>/exclude/<entry point type name>/<exclude rule name>

Overwrite Parameter

Use the overwrite parameter to overwrite a configuration of the same name. Without this parameter, if the import encounters a configuration for a component of the same name, the request will fail.

For example, to import a configuration for a custom match rule named "My Rule" to an application that has an existing "My Rule" custom match rule that you want to overwrite use:

http://appdcontroller.example.com/controller/transactiondetection/Wine+Cellar/custom/nodeJsWeb/My+Rule?overwrite=true

The default is overwrite=false.

  • No labels