Import a Business Application

To import an application configuration, you must be logged in as a user with Administrator user role privileges; see Roles and Permissions. You also need access to a previously exported configuration file.

To import the configuration, follow these steps:

  1. From the Applications tab, click Actions > Import.
  2. Select the XML file that contains the configuration you want to import.
    You can import it into an existing business application or create a new one.
  3. Select the configuration settings you want to import.
    Options include configuration settings for app agents, data collectors, health rules, MDS (scoped instrumentation settings), and more.
    Configuration Type Description
    Backend Match Point Configuration

    It is the backend discovery rule configuration. Splunk AppDynamics discovers backends from exit point instrumentation placed in the application code. An exit point is a precise location in the code where an outbound call is made from an instrumented node.
    Metric Baselines You can import metric baseline values and then see how data in the Metric Browser compare to baseline values. Monitoring baseline deviation exposes performance metrics that might violate your Service Level Agreements (SLAs).
    Analytics Dynamic Service Configuration

    The Analytics configuration may include the following:

    • Transaction Analytics - Configuration: Enable Analytics for specific applications and business transactions.
    • Transaction Analytics - Manual Data Collection: Analytics supports three types of data collectors: method invocation data collector (MIDC), HTTP, and SQL.
    • Log Analytics: Configure source rules to collect data for log analytics.
    • API Keys: Create API authentication keys for users of the Analytics Events API.
    Data Gatherer Configuration

    It is the data collector configuration. Data collectors supplement business transaction and transaction analytics data with application data. The application data adds context to business transaction performance issues. For example, they may show the values of particular parameters or return values for business transactions affected by poor performance.

    This data shows the business context affected by performance issues, such as the specific user, order, or product.
    Agent Configurations Agent configurations instrument your applications.
    MDS Configuration Scoped instrumentation settings.
    Application Components Application components such as web services, message queues, and databases.
    Entry Match Point Configuration The entry match point configuration is a custom match rule (transaction detection rule) that enables you to define criteria for business transaction discovery and naming for an entry point type.
    Health Rules Health rules let you specify the parameters that represent what you consider normal or expected operations for your environment. The parameters rely on metric values, for example, the average response time for a business transaction or CPU utilization for a node.
    EUM Cloud Configuration

    Splunk AppDynamics End User Monitoring (EUM) provides end-to-end visibility on the performance of your web and mobile applications. EUM helps you troubleshoot problems such as slow web responses, Ajax errors, mobile network requests, and IoT application errors. EUM provides metrics on application performance and user activity.
  4. Click OK to start importing.
    The import process first validates the file. As it proceeds, it shows the status for each type of artifact in the Import Application dialog.
  5. Close the Import Application dialog when the import process is complete.
    Note: Application import does not work over HTTPS if the Controller uses a self-signed SSL certificate. Use a trusted, CA-signed certificate instead. See Controller SSL Configuration Properties.