Moogsoft Docs

Upgrade Moogsoft AIOps

This topic describes how to upgrade Moogsoft AIOps to v7.3.x from any of the following versions:

  • v7.0.x

  • v7.1.x

  • v7.2.x

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 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 AIOps server(s) 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: https://speedy.moogsoft.com/installer/. Contact Moogsoft Support for access if you do not already have an account.

  • If you have root access but your Moogsoft AIOps server(s) do not have access to the internet, see "Prepare for an offline upgrade" in RPM - Prepare to upgrade.

Your Moogsoft AIOps 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 AIOps databases.

  • Data ingestion: Server side LAMs.

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

RPM upgrade to Moogsoft AIOps v7.3.x

To perform the RPM upgrade to Moogsoft AIOps v7.3.x, complete the steps in the following documents, in this order:

Tarball upgrade to Moogsoft AIOps v7.3.x

To perform the Tarball upgrade to Moogsoft AIOps v7.3.x, 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.