Skip to main content

Upgrade Moogsoft Enterprise

This topic describes how to upgrade Moogsoft Enterprise to v8.2.0 from any of the following versions:

  • v7.1.x

  • v7.2.x

  • v7.3.x


Users wishing to upgrade from version v8.0.x onward should follow the following process :Patch Moogsoft Enterprise

Saas customers can contact support to request an upgrade, see Upgrading and Updating Your Moogsoft Hosted Instances.

For information on how to upgrade from other versions, see Moogsoft Releases.

For instructions on how to install a distributed high availability (HA) configuration, see Fully Distributed HA Installation.

Your upgrade path depends on your preferred mode of deployment:

  • RPM: Use this method if you have root access to your Moogsoft Enterprise servers and you do not want to change the default installation locations.

  • Tarball: Use this method if you need to run the process as a non-root user, or you want the ability to deploy to a non-default location and install all components under one directory.

    The Tarball installer is hosted on the Moogsoft "speedy" Yum repository: Contact Moogsoft Support for access if you do not already have an account.

  • If you have root access but your Moogsoft Enterprise servers do not have access to the internet, see "Prepare for an offline upgrade" in RPM - Prepare to upgrade.

Your Moogsoft Enterprise deployment is broken up into a set of roles. A role is a functional entity containing components that should always reside on the same server:

  • UI: Nginx, Apache Tomcat, UI integrations.

  • Core: Elasticsearch, Moogfarmd, RabbitMQ, Events Analyser.

  • Databases: MySQL, Moogsoft Enterprise databases.

  • Data ingestion: Server side LAMs.

This process enables you to upgrade the components in each role, whether your Moogsoft Enterprise system is distributed on several servers or installed on a single host.


The implementation of a new Topology API means any old topologies are removed as part of the upgrade. It is important that any recipes using topology in any way are updated once the topologies have been recreated in v8.x.x post-upgrade, before events are sent into MoogFarmD.

Hop limit has been removed from Recipe configurations in Moogsoft Enterprise v8.0.0. You can reconfigure a hop limit if you are using a named or inferred Topology to filter a Recipe.

RPM upgrade to Moogsoft Enterprise v8.2.0

To perform the RPM upgrade to Moogsoft Enterprise v8.2.0, complete the steps in the following documents, in this order:

Tarball upgrade to Moogsoft Enterprise v8.2.0

To perform the Tarball upgrade to Moogsoft Enterprise v8.2.0, complete the steps in the following documents, in this order:

Minimize upgrade downtime

To minimize the amount of downtime required for the upgrade process, follow this process:

  1. Disable historic data retention.

  2. Perform the upgrade according to your chosen method of deployment.

  3. Re-enable the Historic Data Utility.

  4. Let the historic data retention utility process any alerts that have accumulated. This should not take long if the process has been disabled for only a few hours.

Install Moogsoft Add-Ons

Moogsoft periodically releases add-ons to extend and enhance the core Moogsoft Enterprise functionality. For example, new Workflow Engine functions, new Workflow Engines, or Integrations tiles. All add-ons releases are cumulative and include the fixes from previous releases.

Once you have finished upgrading or installing Moogsoft Enterprise, you should install the Moogsoft Enterprise add-ons to ensure you have the latest version.

See Install Moogsoft Add-ons for more information on how to install the Moogsoft Enterprise add-ons.