Moogsoft Docs

Moogsoft AIOps v7.0.0 Updates

Moogsoft has issued the following updates to Moogsoft AIOps 7.0.0. All updates are cumulative and include the fixes from previous releases.

Moogsoft AIOps v7.0.1.9

  • INT-5520: Corrects a JDBC_lam query issue related to an Oracle database.

  • MOOG-13546: Improves validation of the integration name field. Now validation allows only alphanumeric characters and underscores.

  • MOOG-14400: Failover and startup logging of Moogfarmd is now logging the values correctly.

Moogsoft AIOps v7.0.1.8

  • MOOG-13233: Fixes a vulnerability within Tool ChatOps shortcuts.

  • MOOG-13589: A library upgrade for a security issue within the Jackson library.

Moogsoft AIOps v7.0.1.7

  • MOOG-13054:
    • A vulnerability within the internal getTeamList endpoint has been fixed.

    • Security around system settings permissions has been increased.

    • A defect that allowed users without permissions to start and stop services is now resolved.

    • When logging into a LAM configured to use basic authentication on the same host as Moogsoft AIOps, Moogsoft AIOps no longer uses the credentials from the basic authentication request. If you log in to a LAM from a browser using basic authentication, either use "incognito" mode or manually clear the credentials when you are done.

Moogsoft AIOps v7.0.1.6

  • MOOG-12818: On leaving a window the Maintenance Window Manager now creates one Message Bus update for each alert, instead of an update for every thread on each alert.

Moogsoft AIOps v7.0.1.5

Note

Before you update to Moogsoft AIOps v7.0.1.5, back up $MOOGSOFT_HOME/config/system.conf .
After you complete the upgrade steps, restore system.conf before restarting services.

  • MOOG-11283: A number of changes have been made to improve the functioning of Moogsoft AIOps in distributed environments:
    • Situation data is now saved to the persistence store when the process to create or update a Situation fails.

    • The Message Bus is now resilient to network failure and can recover without losing data during the recovery process.

    • When auto failover is enabled, Moogfarmd can now only become active when there is consensus between RabbitMQ and database failover mechanisms.

    • Moogfarmd no longer ignores Situation Closed messages from the Housekeeper Moolet.

    • State persistence is now enabled by default for all Moolets including Cookbook and it is no longer configurable for individual Moolets. The persist_state property is configurable for all Moolets in $MOOGSOFT_HOME/config/system.conf .

    • Creating and merging Situations in some rare scenarios no longer produces Situations with a large number of unrelated alerts.

    • The lifespan management of bot modules is now more reliable and less prone to unexpected errors.

    • When the Maintenance Window Manager Moolet is deactivated and then reactivated it no longer loses the details of active maintenance windows.
    • Existing clusters in a Recipe are no longer overridden on failover.
    • Large Situations now log more informative data.

Moogsoft AIOps v7.0.1.4

  • MOOG-11851: Added support for the Moogsoft AIOps indexer to work with the SaaS deployment architecture.

Moogsoft AIOps v7.0.1.3

  • MOOG- 11362 : A fix that allows invalid filters through the updateMaintenanceWindow Graze endpoint .

Moogsoft AIOps v7.0.1.2

  • MOOG-11615: SaaS customers no longer see an error when performing a user search in the Situation Room and Team Room.

Moogsoft AIOps v7.0.1.1

  • MOOG- 11380: The default SAML configuration in security.conf no longer overwrites existing Moogsoft AIOps users and assigned roles and teams.
  • MOOG-11529: When security.conf is configured to map IdP role and team attributes to roles and teams that do not exist in MoogDb, Apache Tomcat now logs an error message.


For more information see: