Conduct both System Acceptance Testing (SAT) and User Acceptance Testing (UAT) to complete this phase of your migration.
Welcome to the final stop along your cloud migration journey. We recommend doing both System Acceptance Testing (SAT) and User Acceptance Testing (UAT) to complete this validation phase of your migration. Here is a quick refresher on what each of these entail:
System Acceptance Testing (SAT)
Thisis testing conducted on a completely integrated system to evaluate the system's compliance with its specified requirements and ensuring the software does not crash. This testing should be undertaken by the system administrator with the support of the solution provider: in this case, Splunk.
At this point, you should have completed your Splunk environment and data migration. The following listwill guide you through the checks following yourmigration. It includes checks you should consider, not necessarily the exact details to verify each check.Follow this list to ensure all migration steps have been completed, as all migrations could differ in the actual tasks to be performed. We recommend not to beginyourend-user user acceptance testing (UAT)until you feel confident that all relevant checks below are confirmed.
- Confirm index names are migrated and available on premium search heads and IDM
-
Confirm Splunk and Splunkbase apps are installed
-
Confirm Splunk and Splunkbase app customizations are migrated
-
Confirm custom apps are installed and customizations are migrated
-
Confirm DMA is applied
-
Confirm Splunk system/local is migrated (where applicable)
-
Confirm users and customization are migrated, and avoid orphaned saved searches
-
Confirm proper apps / dashboards / reports / alerts / functionality
-
Confirm forwarding is working correctly
-
Confirm inputs are moved to IDM
-
Confirm hosts, sources, source types appear as in your previous Splunk environment
-
Confirm historical data is migrated properly (if applicable)
User Acceptance Testing (UAT)
This consists of verifying that a solution works for the user. This testing should be undertaken by a subject-matter expert (SME), preferably the owner or client of the solution under test. Listed beloware some recommended user acceptance(UAT)test case types.You can use this list and build on it as you execute your UAT testing.
Navigation tasks
Can younavigate through Splunk Cloud Platformas expected? Things you can try and verify:
- Try logging in
- Confirm landing page(s) is as expected
- Confirm you can navigate to and open different apps
- Confirm you can expand results after a search to see fields
- Check for knowledge objects, saved searches, and other items you’d expect to see
Feature availability
Are all the features/functionalities that you used in your previous Splunkenvironment availableas expected in Splunk Cloud Platform?
Behavioral tasks
Do the feature/functionalities/apps behave as expected?For example:
- Dothe premium app(s) work; can youdo what youexpect to do with the apps?
- Do the workflows behave appropriately?
Performance tasks
Is everything executing as expected with no major lags/issues or other obvious performance issues?
Cloud Admin tasks
These scripts are intended to get new Splunk Cloud Platformadminsfamiliar with the differences between operating their previous Splunkenvironment and the new Splunk Cloud Platformstack.
- Try running a new search & creating a dashboard
- Try installing an app
- Try creating a new index
- Try setting retention on an index
- Migrating to Splunk Cloud Platform
- The guided path below provides an overview of how to migrate to Splunk Cloud Platform. In addition, it contains recommendations on best practices, tutorials for getting started, and troubleshooting information for common situations.
- Pages: 7
- Phase 1: Splunk Cloud Platform migration overview
- Create a plan, allocate resources and draw up timelines to ensure a smooth migration to Splunk Cloud Platform.
- Phase 2: Getting started with your Splunk Cloud Platform migration
- Chart your own path to Splunk Cloud Platform or take advantage of Splunk Professional Services teams or Splunk Partners.
- Phase 3: Determining your readiness for Splunk Cloud Platform migration
- Prepare for your migration and set the right expectations based on learning from thousands of migrations across Splunk’s customers.
- Phase 4: Preparing for Splunk Cloud Platform migration
- Learn about blockers or showstoppers and about potential delay causing risks during a migration to Splunk Cloud Platform.
- Phase 5: Migrating to the Splunk Cloud Platform
- Review this checklist of the major milestones in the Splunk Cloud Platform migration process.
- Phase 6: Validating Your Splunk Cloud Platform Deployment
- Conduct both System Acceptance Testing (SAT) and User Acceptance Testing (UAT) to complete this phase of your migration.
- Phase 7: Welcome to Splunk Cloud Platform!
- Now that you have complete the migration to Splunk Cloud Platform, learn what to do next.
