Skip to main content

8.1 Improvements


Due to incompatibilities between the new/upgraded version of RabbitMQ required by/bundled with this release and the old version (3.7.4), 'rolling upgrades' are not supported, and therefore the entire RabbitMQ cluster requires a 'full stop' upgrade. Moogsoft Enterprise SAAS deployments where a local "on-prem LAM-only" environment is also present can stop the local RabbitMQ LAM during the SAAS upgrade to buffer events in the local Rabbit, then restart the LAM when the SAAS upgrade is complete, so no events are lost.

8.1 Improvements

Moogsoft Enterprise v8.1.0 includes the following improvements compared to v8.0.0.


Release Note


It is now possible to expand or collapse list of Impacted Services, Team Rooms, or Situation/Alert Views in the Left Navigation panel.


A 'Situation Client tool' can now be set as a default tool, for easy access in the Situation Room


The maximum number of headings configurable for the Situation Room has been increased.


Updated the health logging for the 'moogpoller' servlet to include active web socket subscription counts and internal queue build up count.


Adds support for an encrypted systemUser password to LDAP; it is enabled by adding or setting the encryptedSystemPassword property in $MOOGSOFT_HOME/config/system.conf, inside the LDAP block.


Adds the ability to control which files can be uploaded to Situation Rooms and Team Rooms based on their content type. This is configured under System Settings -> Customization (all file types are allowed by default if the list is empty).


Introduces an optional password policy for DB Realm users, including configurable complexity via regular expressions.


Improves single sign-on (SSO) configuration so users don't need to re-enter their credentials as often when used with certain IDPs - the 'forceAuth' property is now configurable in any defined 'SAML' realm in the $MOOGSOFT_HOME/config/security.conf file.


Improves the moog_db_validator utility so it identifies valid differences (such as custom_info columns) and those indicating potentially serious issues in the schema (such as missing tables)


Adds the primary_team_id field to all Situation objects as they are processed by Moobots for consistency and reporting purposes.


Updates the Alert Entropy UI to only allow incremental runs, and includes a new default schedule (a daily incremental run at 03:00 with a one day "readage" and a three week "keepage").


Adds the new Cisco Crosswork Data Gateway (CDG) LAM.


Added primary_team_id in graze response of getSituationsDetails.


Adds an event code for API alert modification. A new event code is now added for any API alert modification using updateAlert and updateClosedAlert that does not impact the severity of an alert. Events with this code are filtered out of the UI timeline.


A new MoogDb V2 method resolveAlerts can be used to resolve alerts. It accepts an array of alerts IDs and optional thread entry comment and returns true for a successful request and false for an unsuccessful request.


NGiNX has been upgraded to 1.20.1


The versions of Percona XtraDB Cluster and XtraBackup (as deployed by the install_percona_nodes* scripts) have been upgraded to 5.7.33 and 2.4.23 respectively. Note that the version of XtraBackup deployed by is now explicitly set in the script (rather than pulling the latest available). This is to keep versions in sync with the tarball variant


The minimum JDK version supported and the version shipped is now


Apache-Tomcat has been upgraded to 9.0.43


RabbitMQ has been upgraded to v3.8.16 and Erlang to v23.3.


The list of ciphers accepted by NGiNX has been updated to increase the security of the web server.


The moog_db_split_configurer utility now has an option for setting event batch size : -e,--events_batch_size <value> Number of events/snapshots per batch during deletion (default : 100000) This option sets the batch size used for event/snapshot deletion by the Splitter which, if lowered, may help improve Splitter performance and reduce Database load, particularly in environments where alerts have high event counts.


The process_log entries made by the Splitter have been improved to give more detailed breakdown of tasks, counts and timings as a run progresses.

2.3.5 Add-ons Release

The 2.3.5 release is an add-on to Moogsoft Enterprise 8.1 that includes bug fixes, a new integration, and many new Workflow Actions. See Add-ons v2.3.5 for a list of improvements and fixes.

New integration: Retry Queues

The Retry Queues integration lets you configure Retry Queues used by specific workflow engine functions, notably exportViaRestWithRetry. The standard exportViaRest and sendViaRest functions do not attempt to retry a failed REST request. These actions log the failure, but take no further action. Where an outbound request needs to be retried on failure, then a you should use a retry queue and a retrying function.

See Retry Queues Integration.

New workflow actions

This release includes the following new Workflow Actions: