Configure connections

Reference information about configuring source and destination connections and the prerequisites for using them.

Configure connections

The Connections page enables you to create and manage authenticated connections to your source and destination environments. A source connection links Migration Tool to a Splunk AppDynamics Controller. A destination connection links it to a Splunk Observability Cloud organization.

During Phase 1, create and test each source connection required for discovery and inventory reports. Configure and test the destination connection before you run a report or migration operation that requires Splunk Observability Cloud access.

You must configure at least one source connection and one destination connection before you create a migration job. Migration Tool uses these connections to discover source artifacts and push translated configurations to the destination.

Prerequisites

Ensure that you have:

  • An Admin or Power User role in Splunk Observability Cloud. These roles can view Migration Assistant in the navigation.
  • An Splunk AppDynamics API client name and associated secret. The required source permissions are listed in Add a Source Connection.
  • A Splunk Observability Cloud organization access token with the admin permission. This permission is mandatory for the destination connection and for migration operations that create webhook integrations and Business Transaction rules. See Create and manage organization access tokens.
  • The Controller and organization API endpoints, plus any required firewall or proxy access.

Access the connections page

Access the Connections page from Splunk Observability Cloud.

  1. Log in to the Splunk Observability Cloud with an Admin or Power User role.
  2. Select Data Management > Migration Assistant.
  3. In the left navigation panel, select Connections.
  4. The Connections page opens and displays configured source and destination connections.

Connections page

Connections page details

Reference information about the source and destination connection sections and their table columns.

The Connections page organizes connections into two sections: Source and Destination.

Source connections

The Source section lists all configured Splunk AppDynamics Controller connections. Each source connection represents a Splunk AppDynamics Controller from which you migrate monitoring configurations.

Source connection details

Column Description

Name

The display name you assign to the connection. Select the name to open or edit connection details.

API endpoint

The full URL of the Splunk AppDynamics Controller. Migration Tool uses this URL to connect to the Controller REST API.

Created by

The username or email of the person who created the connection.

Actions

Action buttons to edit or delete the connection.

Destination connections

The Destination section lists all configured Splunk Observability Cloud organization connections. Each destination connection represents an organization to which Migration Tool pushes translated configurations.

Destination connection details

Column Description

Name

The display name you assign to the connection. Select the name to open or edit connection details.

API endpoint

The full URL of the Splunk Observability Cloud organization. You can find the endpoint on the My Profile > Organizations page.

Created by

The username or email of the person who created the connection.

Actions

Action buttons to edit or delete the connection.

Add a source connection

Add a Splunk AppDynamics Controller as a source connection.

To add a new Splunk AppDynamics Controller as a source:

  1. Select + Add Source on the Connections page. The system opens the Add Source Connection dialog box.

    Add Source Connection dialog box
  2. Fill in the following fields to configure a source connection:
    Field Description

    Connection name

    Enter a descriptive name. This name appears in the Source drop-down when you create a migration job.

    API endpoint

    Enter the full URL of the Splunk AppDynamics Controller, including the protocol.

    Access token
    Enter the API client secret associated with the API client name. Migration Tool uses the API client name and secret to generate an OAuth token for authenticated API access.
    Note: Note: Ensure the API client has sufficient permissions to read applications, Health Rules, dashboards, and HTTP Request Templates from the Splunk AppDynamics Controller. Assign these roles to the API client: Account Owner Applications & Dashboards Viewer DB Monitoring User Dashboards Viewer Server Monitoring User
  3. Select Add connection to create the connection.
  4. The system validates the connection and adds it to the Source connections list.

Test source connection

Test a saved Splunk AppDynamics Controller source connection.

Use the test option to verify that Migration Tool can reach the Splunk AppDynamics Controller and authenticate with the saved source connection credentials.

  1. In the Source connections section, locate the source connection that you want to validate.
  2. Select the test connection action for that connection.
  3. Wait for the validation to complete. The system checks the Controller endpoint, authentication details, and API access.
  4. If the test is successful, the connection is ready to use when creating a migration job. If the test fails, verify the API endpoint, API client credentials, required permissions, and network connectivity, then edit the connection and test again.

Add a destination connection

Add a Splunk Observability Cloud organization as a destination connection.

To add a new Splunk Observability Cloud organization as a destination:

  1. Fill in the following fields to configure a destination connection:
    Field Description

    Connection name

    Enter a descriptive name. This name appears in the Destination drop-down when you create a migration job.

    API endpoint

    Enter the full URL of the Splunk Observability Cloud organization. You can find the endpoint on the My Profile > Organizations page.

    Access token

    Enter a Splunk Observability Cloud organization access token with the admin permission. This permission is mandatory for the destination connection and for migration operations that create webhook integrations and Business Transaction rules. See Create and manage organization access tokens.

    Add Destination Connection dialog box
  2. Select Save to create the connection.
  3. The system validates the connection and adds it to the Destination connections list.

Test destination connection

Test a saved Splunk Observability Cloud destination connection.

Use the test option to confirm that Migration Tool can reach the Splunk Observability Cloud organization and authenticate with the saved destination access token.

  1. In the Destination connections section, locate the destination connection that you want to validate.
  2. Select the test connection action for that connection.
  3. Wait for the validation to complete. The system checks the organization endpoint, access token, and required API permissions.
  4. If the test is successful, the destination connection is ready to receive translated migration configurations. If the test fails, verify the API endpoint, regenerate or update the access token, confirm that the token has the mandatory admin permission, and test the connection again.

Managing existing connections

Reference information about editing and deleting existing source and destination connections.

Edit a connection

  1. Locate the connection in the Source or Destination section.
  2. Select the Edit button.
  3. Update the fields as needed, such as rotating a token or updating a URL.
  4. Select Save to apply the changes.

If a connection is already used in at least one migration, you cannot update the connection URL or connection name.

Delete a connection

  1. Locate the connection in the Source or Destination section.
  2. Select the delete action button.
  3. Confirm the deletion when prompted.
Note:
  • Deleting a connection deactivates it rather than permanently removing it; the historical record is retained.
  • Deleting a source connection also removes the associated discovery and analytics inventory. If the connection is reactivated, the inventory must be rebuilt.
  • Deleting a connection does not affect completed migration jobs. However, in-progress jobs that use the deleted connection can fail. Confirm that no active jobs reference the connection before deleting it.

Best practices

Reference information about recommended practices for configuring and testing connections.

Best practices

  • Use descriptive names to distinguish environments.
  • Rotate API client secrets and access tokens regularly.
  • Create separate connections for production, staging, and development.
  • Test each connection before running a migration job.