Update versions

An update version is determined by the build and revision number in its versioning scheme, which includes major, minor, and revision identifiers as well as the build number. For example, the revision and build number 1.1027 identifies update The major and minor identifiers of the update must match the version of the AppMon system on which it is installed. For example, you can install update on an AppMon system, but not on version

Only one update can be active on an AppMon system at a given time. Therefore, activating an update deactivates an older one if present. Update files have the extension .dtf and are usually distributed in a .zip archive with a checksum file and release notes.

Difference between updates, plugins, FastPacks, and product upgrades

  • Updates: Smaller changes in the software, usually bug fixes or small enhancements, are indicated by a different build number or revision number, for example, from to See Versioning scheme for more information. Plugins: Supplemental product libraries that extend AppMon with features and functions beyond the functionality in the installed product. Plugins are imported into the product from the Plugins pane of the Dynatrace Server Settings dialog box, which is accessible from the Client. See Plugins for more information.

FastPacks: Downloadable packages that can contain resources such as preconfigured plugins, sensor packs, dashboards, and System Profiles. A FastPack bundles these different resources into one installation file that can be imported and installed into AppMon just like a plugin. See Building FastPacks for more details.

Upgrade: Requires a completely different installation process from an update, plugin, or FastPack. A product upgrade must be installed to a separate directory structure and settings and data needs to be migrated from the old to the new version to persist your data. See Upgrade and Migration Guide for more details.

Upgrades are significant changes in the software, including new features and enhancements. They are indicated by a different major or minor number. For example, from to

When AppMon versions differs on major, components such as the Server or Collector are normally compatible, but this is not guaranteed. Major and minor version are part of the default installation path, signaling that software differing therein must be installed into different directories.


The revision does not appear in the default installation path to accommodate for in-place updates on the revision level.