Upgrade your deployment
During this phase, the platform, infrastructure, and monitoring components are migrated. This includes licensing, SaaS environments, infrastructure, Dynatrace configurations, integrations and all application or infrastructure monitoring sources.
First, the new Dynatrace SaaS platform and accompanying infrastructure should be prepared. Next, the configuration, integrations, and applications should be systematically migrated.
Step 1 - Prepare
Main objectives of this step:
Clarify potential changes in licensing
Provision Dynatrace environment
Deploy necessary infrastructure
This step focuses on preparing the new Dynatrace platform (including the SaaS environment), all supporting infrastructure components and configurations to support ActiveGates, and required network flows.
Request the provisioning of Dynatrace environments
Dynatrace provisions new SaaS environments in your account for you in the available hyper scaler and region. This requires the setup of proper licensing for your SaaS environments and includes the dual running of the Managed cluster. Share information on the planned migration timeline and expected growth.
Configure new environments
After the SaaS environment is provisioned, environment configuration is addressed. This includes:
Provisioning infrastructure for ActiveGate instances
Configuring proxy/DNS if needed
Checking with the Dynatrace Support team if custom FeatureFlags have to be set
Validating that licensing is correctly set up for all of your environments
Step 2 - Execute
Main objectives of this step:
Migrate infrastructure monitoring
Migrate application monitoring (OneAgents)
In this step, all monitoring configuration is applied to the Dynatrace environment. Furthermore, the below actions are advised:
A Dynatrace environment may contain many individual configuration items. Manual migration may cause delays in the project and increase the likelihood of errors. Follow the procedure described in Migrate configuration to migrate the configuration most efficiently.
Once configurations have been transferred, it is important to validate that all the relevant configurations have been migrated successfully. This will ensure that the environment has all the necessary configurations to continue processing data once the OneAgents are switched over to the SaaS platform and provides a seamless cutover for Dynatrace users.
For the most critical configurations, review them manually by comparing your environments. You can also use a JSON diff combined with Dynatrace REST API.
Once the migrated configuration has been validated, the Dynatrace SaaS environment is ready to start receiving OneAgent traffic.
The OneAgent migration involves the reconfiguration or reinstallation of all OneAgents from the Dynatrace Managed, to the new SaaS environment. This step requires careful planning and coordination. Take into consideration the deployment and maintenance procedures of the wider application environment.
OneAgents should be migrated as soon as the configuration migration has been completed. This will minimize the delta between the environments and will provide for the smoothest transition to the new platform.
A series of steps is repeated for every Application to be migrated. Based on the priority-based plan, migrate each application with the following steps:
Reconfigure the OneAgent to the new Dynatrace environment
All OneAgents deployed in the customer environment must be reconfigured to point to the new Dynatrace environment. OneAgent may be deployed on cloud platforms, container platforms, or operating systems.
There are two approaches for redirecting OneAgents to the new SaaS environment:
- Update and reconfigure OneAgent in place (recommended) - for details, see Migrate OneAgent
We recommend that you use the automated solution. Also ensure that Host Group, Network Zone, and Custom Metadata are set correctly during installation, as per the architectural design created in the upgrade guide.
Restart Application Processes and validate those applications observed with the Dynatrace environment
OneAgent injection into monitored processes only happens during application startup, and until the application processes are restarted, the OneAgent will continue to point to the Dynatrace Managed environment. After the OneAgents have been reconfigured, you must restart all application processes where OneAgent is configured in the full stack for deep application monitoring.
As the last step of the migration, validate that the application data is flowing seamlessly into the new environment, hosts, processes, services, and applications appear as expected, custom settings are in place and alerting/notifications are configured the same.
Review data in the SaaS environment to ensure everything looks correct and data and metrics are flowing as expected.
We recommend regularly validating the state of the upgrade by:
Cross-checking configuration in the old environment and new environments, assure that integrations work and that ActiveGates is configured the right way
Engaging with your teams using Dynatrace and letting them check that all monitoring is set up in the way they expect
Migrate Dynatrace Operator
If you deployed Dynatrace Operator to a Kubernetes cluster, you can migrate Kubernetes monitoring from your Managed cluster to your SaaS environment by reconfiguring the Dynatrace Operator deployment.
Step 3 - Integrate
Main objectives of this step:
Update external integrations to communicate with SaaS environments
Ensure your monitoring and alerting landscape is re-integrated after migration
All third-party integrations previously used with the Dynatrace Managed cluster need to be updated and validated. Configure and review all integrations and ensure that end-to-end workflows are operational. Examples include service management platforms, automation platforms for automated remediation, CI/CD pipelines, and reporting systems.
Update automation that uses Dynatrace API
Any API access should be updated to use the new environment. This requires the generation of new API tokens, as existing tokens can’t be migrated due to security reasons.
Visit the Upgrade to SaaS forum to ask questions, get answers, and share what you've learned with others.