Upgrade private Synthetic locations
- Latest Dynatrace
- How-to guide
- 3-min read
Update Synthetic Engines
Synthetic Engines running on private locations must be at version 1.347+ to support browser monitors on Latest Dynatrace. Engines below this version cannot execute monitors with the latest RUM JavaScript enabled.
Check engine versions
Use the readiness dashboard to see the engine version for every private location. The dashboard shows:
- Not ready: at least one reporting engine is below version 1.347. Update the engines listed in the Engines to update column.
- Engine versions ready: all reporting engines run version 1.347+. No action needed for standard locations.
You can also query engine versions directly:
smartscapeNodes SYNTHETIC_ENGINE| fieldsAdd version = dt.synthetic_engine.version| fields id, version
Update the engines
Update each engine earlier than version 1.347 following your standard deployment procedure. After the update, confirm that the engine is healthy and reporting in 
Synthetic under Private locations.
Update containerized locations (Kubernetes and OpenShift)
Containerized locations on Kubernetes or OpenShift require an additional step that the readiness dashboard cannot verify. Even if the engine version is ready, the location's Synthetic metric adapter must be compatible with the Grail Query API to provide utilization data and automatic scaling.
For each containerized location, choose one of these options:
- Redeploy the location with the updated configuration, or
- Migrate the Synthetic metric adapter to the Grail Query API.
For instructions, see Migrate the Synthetic metric adapter to the Grail Query API.
After the change, confirm that:
- The ActiveGate pods and Synthetic metric adapter are running.
- Utilization data is available in Synthetic.
Standard private locations don't need to be redeployed because they were created in an earlier Dynatrace version. Redeployment or Synthetic metric adapter migration applies only to Kubernetes and OpenShift locations.
Verify the upgrade
For every private location, confirm that all associated Synthetic Engines are healthy, reporting, and run version 1.347+, and that a representative monitor executes successfully from each location. For Kubernetes and OpenShift locations, also confirm that the adapter migration or redeployment is complete.