Assess the Splunk AppDynamics environment

Complete this checklist for every Splunk AppDynamics SaaS Controller and account in the initial migration scope. Do not record API tokens or other credential values in the assessment.

• Record the complete Splunk AppDynamics SaaS Controller URL.
• Confirm that the Controller is an Splunk AppDynamics SaaS deployment.
• Record the Controller region.
• Record the Controller version or build information, when available.
• Compare the deployment and region with Supported Migration Scope and Limitations.
• Record the Splunk AppDynamics account name and confirm that the account belongs to the approved migration scope.
• Identify the Controller administrator, account administrator, and API credential owner.
• Confirm that the source credential can read the applications and configuration required for discovery.
• Record any account or permission restriction that might prevent complete discovery.
• Record the licensed monitoring domains, such as Application Performance Monitoring, Infrastructure Monitoring, End User Monitoring, Database Monitoring, Synthetic Monitoring, and application security.
• Identify the monitoring domains that the current migration includes.
• Record the current license or entitlement utilization for each relevant monitoring domain, when available.
• Ask the account or platform owner to review any utilization or entitlement constraint that might affect the migration.
• Record the total number of applications that the Controller reports.
• After generating the Application Discovery report, compare its application count with the Controller count and investigate any difference.
• Record the current data-retention settings.
• Identify requirements for continued access to historical Splunk AppDynamics metrics, transaction snapshots, events, logs, configuration, or audit information.
• Assign an owner and retention period for historical information that must remain available after migration.
• Record every missing, unsupported, or unclear item, its potential effect, its owner, the required action, and whether it blocks the phase.
• Ask the Splunk AppDynamics administrator and migration owner to review the completed assessment.

Complete the assessment when you document Controller, account, licensing, application-count, access, and retention information and assign an owner and action to every unresolved finding.