Bug Fixes

MOOG-12802

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

MOOG-12694

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.

MOOG-12617

Hazelcast persistence is now handling objects created in JavaScript correctly.

MOOG-12587

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

MOOG-12582

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.

MOOG-12435

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

MOOG-12389

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

MOOG-12299

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

MOOG-12277

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

MOOG-12200

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

MOOG-12182

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

MOOG-12123

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

MOOG-12122

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.

MOOG-12112

Switching the UI Dashboards feature toggle off now re-routes any requests to https://example.com/#/dashboard* to https://example.com/#/.

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.

MOOG-12086

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.

MOOG-12056

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

MOOG-11894

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

MOOG-11892

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

MOOG-11852

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.

MOOG-11816

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.

MOOG-11813

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

MOOG-11762

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

MOOG-11575

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.

MOOG-11066

The following endpoints now accept multiple teams:

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)'.

MOOG-12281

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

INT-5022

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.

INT-5014

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).

INT-4986

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

INT-4947

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

INT-4934

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

INT-4908

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

INT-4869

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

INT-4848

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

INT-4505

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

INT-4503

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

INT-4492

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"  :"jane_citizen@example.com",
   "type"     :"rfc822",
   "group"    :false
}]

INT-4485

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.

INT-4473

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

INT-4470

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