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)
This is 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 list will guide you through the checks following your migration. 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 begin your end-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 below are some recommended user acceptance (UAT) test case types. You can use this list and build on it as you execute your UAT testing.
Can you navigate through Splunk Cloud Platform as 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
Are all the features/functionalities that you used in your previous Splunk environment available as expected in Splunk Cloud Platform?
Do the feature/functionalities/apps behave as expected? For example:
- Do the premium app(s) work; can you do what you expect to do with the apps?
- Do the workflows behave appropriately?
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 Platform admins familiar with the differences between operating their previous Splunk environment and the new Splunk Cloud Platform stack.
- 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