Moogsoft Docs

Bug Fixes

Moogsoft AIOps v7.2.0 contains the following new features. See Graze API and MoogDb V2 for details of changed endpoints and methods.


Release Note


The root directory can no longer be used for tgz installations. Any other directory with the proper permissions can be used.


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.


Hazelcast persistence is now handling objects created in JavaScript correctly.


An issue that caused an occasional UI problem when clicking a node in Timeline has been resolved.


Viewing Situations and marking alerts as PRC in Situations that have already been moved to the historic database now inserts data into the appropriate historic database table.


The database pool no longer eagerly creates connections at application startup.


Closed alerts from a previously closed Situation are no longer added to an open Situation.


SAML sign-in failure now presents an error page instead of an endless loop of login retries.


Text relating to some radio buttons in UI system settings is no longer misaligned.


Persistence serialization is now less strict in terms of allowed object types.


The Labs section of the UI now renders correctly in the Dark theme.


The display of alert details in the UI has been improved.


When a Situation is reopened the status is now correctly set to Open. This allows operations to be performed on reopened Situations including adding alerts.


Switching the UI Dashboards feature toggle off now re-routes any requests to* to

It also changes any roles and teams that have dashboards as landing ages to inherit from the system configuration, and if the system configuration has a dashboard as the landing page, it is set to the Summary page.


The behavior of the message_persistence setting in system.conf has changed. It determines whether messages sent by Moogsoft AIOps components are persisted to disk by RabbitMQ for durability and is now enabled by default.

Moogfarmd and Tomcat now create and use durable message queues in RabbitMQ by default. It is no longer determined by the message_persistence setting.


Installing Moogsoft AIOps RPMs using Yum now always creates rpmsave files for config and bot files.


There is now increased persistence store throughput, to improve performance under heavy load.


A defect that allowed a closed Situation to be resolved using the resolveSituation Graze endpoint and MoogDb method has been resolved.


Read-only database connections are no longer valid connections.

On communication failure, a database connection tries to auto-recover, by reconnecting to any valid available connection until successful.


When logging into a LAM configured to use basic authentication on the same host as Moogsoft AIOps, credentials from the basic authentication request are no longer used.

It is recommended that incognito mode is used in a browser when logging into a LAM with basic authentication, or saved credentials are cleared manually afterwards.


Support for Google authentication and URL user profile images have been removed.


A file can no longer be uploaded to the Situation Room while another file upload is still in progress.


An SQL exception is no longer displayed when a column referring to a custom_info field is modified. It is no longer possible to modify the type of a custom column and an appropriate validation error is raised.


The following endpoints now accept multiple teams:

  • getServiceSituationPerTeamStats

  • getSeveritySituationPerTeamStats

  • getStatusSituationPerTeamStats

The target returned now includes the name of the statistic and the affected team.

When the aggregation option of 'sum' is selected for team statistics, the target string returned is now in the form 'Statistic (Team_A/Team_B)'.


A defect that allowed users without permissions to start and stop services has been resolved.


The new moolet_informs permission has been added to users with sig_modify and alert_modify permissions. This allows them to run xMatters Alert and Situation tools.


If a polling LAM's recovery interval is greater than or equal to the request interval, it is now set to the request interval divided by three (rounded down to the nearest integer).


When an active polling LAM is restarted within a failover window, its HA state information is no longer cleared.


The xMatters default proxy port in the Moobot is now type integer, not string.


A problem where Zabbix connections were killed by the server and not reinitialised by the LAM has been resolved.


Tools > Engage xMatters Group now works correctly in the UI for alerts and Situations.


A problem causing inconsistent acknowledgment in the RabbitMQ LAM has been resolved.


The body filter in the Email LAM is now case insensitive.


The Dyntrace Notification LAM now sends a clear event when a Dynatrace alert is resolved.


The HP NNMi LAM now sends clear events when incidents are closed.


The Email integration now includes CC and BCC in the event payload and the event's custom_info has been corrected. To, CC and BCC are now represented as lists and distinguish between address, personal and groups. For example:

"cc": [{
   "personal" :"Jane Citizen",
   "address"  :"",
   "type"     :"rfc822",
   "group"    :false


The VMware vRealize LogInsight integration has been updated to include requests overlap functionality. The last poll time is now persisted when a poll returns no events and a pagination issue has been fixed.


The Email LAM body filter now works correctly when retrieving unread email messages.


The recipient filter in the Email LAM TO, CC and BCC fields no longer fails with a ClassCastException in some circumstances.