7.ActiveGate 升级规划

7.ActiveGate 升级规划

GSP-UPG-217_ActiveGate Upgrade Planning
Environment ActiveGates are key features in SaaS traffic management and configuration.
While planning your upgrade to the SaaS platform, you’ll want to create an up-to-date list of all current ActiveGate Instances, note which modules and extensions are enabled, and, in the case of extensions, create a plan to assign them to new ActiveGates.
For more information about ActiveGate extensions, please reference our online documentation.
On the Dynatrace SaaS platform, custom SSL certificates are not supported for the SaaS UI.
However, custom SSL certificates can be provided for ActiveGates.
While creating your plan, identify any existing ActiveGates that have custom SSL certificates associated with them, and plan to have new SSL certificates issued and installed in the SaaS environment.
Please see the online documentation for more specific information about associating custom SSL certificates with environment ActiveGates.
Once you have identified your existing ActiveGate layout and configuration, create your plan to provision new ActiveGates in your SaaS environment.
Existing Managed ActiveGates should be decommissioned once the migration is complete: this ensures that current Dynatrace monitoring is uninterrupted.
Environment ActiveGates are designed for multiple purposes, and some require dedicated ActiveGates.
For example, if you have Cluster ActiveGates configured to run synthetic monitors from a private location, each instance will require a new Environment ActiveGate deployment.
For more in-depth information about ActiveGate purposes, please see our online documentation.
While planning, identify the required firewall rules and proxy configuration for OneAgent to communicate with the new ActiveGates and outbound communication from the ActiveGates to the Dynatrace SaaS environment.
Any key integrations with third-party platforms should also be considered.
The goal should be to optimize and minimize bandwidth usage by deploying the correct number of ActiveGates in each data center and enforcing the use of network zone.
When sizing ActiveGates, ensure sufficient capacity for failure events by provisioning at least two ActiveGates per data center, with additional instances based on capacity requirements.
Keep in mind that additional ActiveGates may be required for synthetic testing, mainframe management, or dedicated to extensions.
As mentioned, bandwidth usage can be managed by defining and implementing SaaS network zones.
Network zones represent your network’s architecture and route telemetry data from OneAgent to your Dynatrace Cluster.
Network zones define which ActiveGates should be used by OneAgents, to avoid unnecessary network traffic across data centers and network regions.
Without network zones, all of your OneAgents can reach your ActiveGates that are routing traffic to Dynatrace.
Since every OneAgent can connect to any ActiveGate, it is possible for a OneAgent to connect to an ActiveGate hosted in another region, producing unnecessary traffic or delays.
Network zones prevent inefficient connections by defining the ActiveGate that each OneAgent should use.
You can also set ActiveGates in other zones as a backup option if primary ActiveGates are unavailable.
Learn more about configuring Network Zones through our online documentation.
In addition to ensuring sufficient ActiveGate capacity, it is also important to plan for the increased outbound bandwidth usage that may result from the relocation of the Dynatrace platform to SaaS.
And finally, remember that OneAgent traffic will not be automatically routed to SaaS after installing the new ActiveGates.
OneAgents will need to be directed to the new ActiveGates or SaaS tenant.