One of the great things of platform-as-a-service environments like Cloud Foundry, Azure, or OpenShift is their ability to automatically scale your applications. For instance, you can add more application instances to handle increased traffic and demand. However, with application instances spun up and down automatically in your production environment you need to ensure that your dynamically created application instances conform to what has been tested in your pre-production environment.
With this goal in mind, we’ve recently introduced a major enhancement to the Dynatrace OneAgent update mechanism. You can now control the default version of OneAgent that is automatically applied to all new hosts and applications that Dynatrace detects in your environment.
To specify the default install version for new hosts and applications
- Go to Settings > Preferences > OneAgent updates.
- Disable automatic OneAgent updates by setting the Automatically update all OneAgent instances switch to the Off position.
- From the drop-down list, select the OneAgent version that should be installed on all newly detected hosts in your environment (for example, version 1.125.149).
Note: You can override the global OneAgent updates setting for individual hosts by going to Settings > Monitoring overview > Hosts and then adjusting the setting on individual host pages. This will enable you to control auto-updates for individual hosts.
This enhancement allows you to control the version of OneAgent that is used for monitoring new hosts that are detected in your environment. This applies to automatically created Cloud Foundry or Azure application instances that are created to handle load spikes. The specified OneAgent version is also applied if you restart any Cloud Foundry or Azure applications.
Note: The default OneAgent install-version feature is not limited to Dynatrace PaaS integrations. The specified standard agent version is applied to all your hosts and is also used, e.g., when installing Dynatrace OneAgent on your hosts.