Page tree
Skip to end of metadata
Go to start of metadata

Moogsoft AIOps V6.2.0 ESR 6

Moogsoft AIOps V6.2.0 ESR 6 is an Enterprise Stability Release release with new features including Probable Root Cause (PRC) and the mobile version of Moogsoft AIOps.

For information on previous Enterprise Stability Releases or on Edge Releases, see AIOps Releases.

The "focus" of the release (via radar/spider chart) in terms of ticket distribution covers 5 focus areas:

  • Roadmap
  • Customer Request
  • Speed of Deployment
  • General Enhancement
  • Maintenance


Release Considerations

The following changes should be taken into consideration for this release:

  • RabbitMQ has been upgraded to 3.6.10. This requires a new yum repo to be added (see the Pre-Install pages or the Upgrade pages as appropriate for details).
  • The Situation and Alert Auto-Close feature is now enabled by default.
    • Situations that have not been updated for a day will be auto-closed (limited to 1000 per attempt) along with all their member alerts.
    • Alerts older than a day and with clear severity will be auto-closed (limited to 1000 per attempt).
  • For consistency some Graze and MoogDb.V2 endpoints now return sitn_id instead of situation_id or sig_id
    • getTeamSituationIds - now returns sitn_ids
    • getActiveSituationIds - now returns sitn_ids
    • getSituationIds - now returns sitn_ids
    • createSituation - now returns sitn_id
    • getActiveSituationIds - now returns sitn_ids
    • getSituationDetails - now returns sitn_id
    • getTeamSituationIds - now returns sitn_ids
    • mergeSituations - now returns sitn_id
    • getSituationIds - now return sitn_ids
    • getAlertDetails - now returns active_sitn_list

Upcoming Release Considerations:

In an upcoming Edge release and for the 6.3.0 release, we will be moving to MySQL 5.7 as the supported database version

The latest version of v6.2.0 is v6.2.0.5 and is the version now available. It contains the following improvements and bug fixes since v6.2.0.2:

  • MOOG-7586: moog_farmd : "Query leak" - increasing query load from moog_farmd to moogdb
  • MOOG-7629: [ServiceNow] Integration fails to install

It also includes all the improvements and bug fixes included with v6.2.0.2:

  • MOOG-6394 - Situation & Alert Details Dialogs now support copy & paste
  • MOOG-7457 - Maintenance Mode UI : Start and end time columns now show the correct start and end time
  • MOOG-7447 - Advanced URL filters now work
  • MOOG-7455 - LDAP : assignTeam no longer fails if the ldap group name in the roleMap is also in the teamMap
  • MOOG-7454 - LAMs now work in a SAML-enabled deployment
  • INT-2982 - REST Client LAM passive -> active now working
  • MOOG-7448 - Exceptions related to SituationRootCause moolet in moogfarmd log are now fixed


Install & Upgrade 

For installation instructions please click here Upgrade instructions are available on the linked child page(s).

Please note: We only recommend upgrading an Edge release incrementally to another Edge release

For more information about upgrading for ESR and Edge releases see Moogsoft AIOps Releases and Versioning.

Highlights

The highlights of this release are shown in the table below:

KeyRelease Note
MOOG-5976

Probable Root Cause (PRC)

Probable Root Cause is a machine learning process that identifies which Alerts are root causes of a Situation. PRC looks for patterns in user supplied feedback.

MOOG-6496

Mobile Beta Version

A mobile version of Moogsoft AIOps has been developed to enable DevOps teams to resolve incidents at any time and anywhere from their cellphones. For more information see Moogsoft AIOps for Mobile.


New Features

The new features included in this release are shown in the table below:

KeyRelease Note
MOOG-4740

It is now possible to synchronise teams with LDAP, including synchronising user team data. This can be set up using the new assignTeams config block available in security.conf.

Example configuration:

assignTeams :{
    teamMap: {
      "ldap-group-name": "Team name",
      "yet_another_group": "Another team"
    },
    useGroupName : true,
    createNewTeams: false
}

For more information, see: Security Configuration

MOOG-7104

A new notification service has been added to Moogsoft AIOps. This will allow SMS messages to be sent to your AIOps users when they are assigned a Situation, invited to a Situation Room or when critical Situations occur for your team.

This service is not enabled by default. For credentials to enable this alpha offering, email support@moogsoft.com.


New Integrations

The following integrations have been added as part of this release:

KeyRelease Note
INT-938

A beta version of VMWare vRealize Log Insight LAM and its Solution Pak have been added. See vRealize Log Insight for more information.

INT-1001

A beta version of Dynatrace APM Plugin Solution Pak has been added. See Dynatrace APM Plugin for more information.

INT-1206

A beta version of CA Spectrum LAM and its Solution Pak have been added. See CA Spectrum LAM for more information.

INT-1633

A beta version of VMWare vSphere LAM and its Solution Pak have been added. See vSphere LAM for more information.

Improvements

The following improvments have been made as part of this release:

KeyRelease Note
MOOG-3512

MooMS SSL Support

RabbitMQ may now be run in SSL mode. New configuration has been added to $MOOGSOFT_HOME/config/system.conf to allow AIOPs components such as moogfarmd to communicate with an SSL-enabled RabbitMQ instance. More information here: https://docs.moogsoft.com/display/060200/Message+System+SSL

MOOG-5293

Improve management of session cookie

The cookie used to track a user's session on the front-end is now managed on the server-side.

  • The cookie is no longer available to the client-side application
  • The cookie will only be sent over HTTPS
  • The cookie is not sent to any third party (cross-origin requests)

There is no change to Graze authentication.

MOOG-5454

PRC Archiver changes

If PRC is enabled, Archiver will now save all of the relevant PRC-marked data that is useful for training PRC into separate tables in the database. Previously this data would have been deleted.

When PRC is retrained, it will now look in both the 'live' tables and the 'archived' tables for training data. This ensures the accuracy of PRC remains as high as possible.

MOOG-5974

Added remove method for the MooBot constants module that allow user to remove key/value pair.

See constants.remove() under Constants

MOOG-6366

Remove the configdiff functionality from the init scripts

The 'configdiff' utility in the moog_init_server.sh has been removed. This was previously used to help merge in differences between new versions of files with customisations but was not user-friendly.

As of 6.2.0, '.rpmsave' versions of files will need to be manually merged/compared with the new versions of those files (any new properties should be added to the older versions of the files).

An example of the process to do this:

  • Rename the new versions of the files (without the .rpmsave extension) to end with '.bak'
  • Merge the .rpmsave file with the new '.bak' file by adding new properties/config where needed so the structure matches the new version of the file
  • Rename the .rpmsave file to delete the '.rpmsave' extension

See the Upgrade Documentation

MOOG-6610

A new evaluateFilter() method is available for Events, Alerts and Situations.
It allows users to evaluate an Event/Alert/Situation against a Filter and return 'true' if it matches.

For example:

var result = alert.evaluateFilter("description matches 'abc[0-9]'");
MOOG-6611

For SAML2-enabled instances the user will now see a confirmation page when they log out or when the session expires.

The new logout page is included in the updated web.conf configuration. Changes to web.conf may be required when updating from an older version of Moogsoft AIOps to enable logout page.

MOOG-6663

Upgrade RabbitMQ to 3.6.10

As of this release the required version of RabbitMQ has been upgraded to version 3.6.10.
This is to fix several security vulnerabilities. See: CVE-2017-4965CVE-2017-4967CVE-2017-4966.
Please note that this change impacts both clean installation and upgrade of Moogsoft AIOps.

  • for clean installation a new RabbitMQ yum repository is now used - see Install Documentation
  • for an upgrade the rabbitmq-server service must be restarted and there are special considerations if a rabbitmq cluster is being used - see Upgrade Documentation
MOOG-6723

You can now use SQL-like filter conditions similar to URL or Cookbook filters instead of JSON formatted filters in the following Graze endpoints:

  • getAlertIds
    • Example curl request to get the first 20 alert_ids with query: agent != SYSLOG AND description matches 'AUTH-SERVICE':
      curl -G -u graze:graze -k -v "https://localhost/graze/v1/getAlertIds" \
      --data-urlencode 'query=agent!=SYSLOG and description matches "AUTH-SERVICE"' --data-urlencode 'limit=20'
  • getSituationIds
    • Example curl request to get the first 20 situation_ids with query: description = 'test1' OR queue = 5:
      curl -G -u graze:graze -k -v "https://localhost/graze/v1/getSituationIds" \
      --data-urlencode 'query=description="test1" or queue = 5' --data-urlencode 'limit=20'
  • createMaintenanceWindow
    • The 'filter' parameter now accepts a string (SQL-format filter) instead of an object (old style JSON-format filter)
    • Example curl request to create a window with filter: source = 'server1' AND external_id IN ('value1', 'value2', 'value3'):
      curl -X POST -u graze:graze -k -v "https://localhost/graze/v1/createMaintenanceWindow" \
      -H "Content-Type: application/json; charset=UTF-8" -d '{"name":"window1", "description":"window1", \
      "filter": "source = \"server1\" and external_id in (\"value1\", \"value2\", \"value3\")", \
      "start_date_time":1473849237, "duration": 55800, "forward_alerts":false}'

      The JSON-formatted filters are still available for use.

MOOG-6724

The following Graze endpoints are now also available in the Moobot moogdb module:

  • assignAndAcknowledgeAlert(Long alertId, Integer userid) returns boolean
  • assignAndAcknowledgeAlert(Long alertId, String username) returns boolean
  • assignAndAcknowledgeSituation(Long alertId, Integer userid) returns boolean
  • assignAndAcknowledgeSituation(Long alertId, String username) returns boolean
  • createUser(userObj) returns boolean
  • createMaintenanceWindow(maintenanceWindowObj) returns boolean
  • createTeam(teamObj) returns ** boolean
  • deleteMaintenanceWindow(Long maintenanceWindowId) returns boolean
  • getActiveSituationIds()
  • getAlertids(String query, Integer limit)
  • getMaintenanceWindows(Integer start, Integer limit)
  • getSituationIds(String query, Integer limit)
  • getTeamSituationIds(String teamName, Integer limit)
  • updateTeam(teamObj) returns boolean

Please see the following page for details on all the functions available: MoogDb.V2

MOOG-6741

The REST module used in Moobots now has a default timeout of 120s to prevent connections being held indefinitely.

MOOG-6809

An improvement has been made which ensures that the Service features of the Workbench are available to customers who do not use the Team Service Filter feature introduced in V6.

If the Team's Services Filter is not used/populated, any Service impacted by Situations assigned to your Team will be displayed in the 'Services Overview' on the Summary Page and 'Services Impacted' in the left navigation menu.


MOOG-6844

Enable graze to get/delete maintenance windows based on a query

Two new graze end points where added:

  • findMaintenanceWindows - To find any maintenance windows. The arguments are:
    • filter A filter string (Something like: starttime > xxxx AND name matches yyy)
    • limit The maximal number of results to get back. (100 by default)
  • deleteMaintenanceWindows - To delete a bulk of maintenance windows. The arguments are:
    • filter A filter string (Something like: starttime > xxxx AND name matches yyy)
    • limit The maximal number of results to get back. (100 by default)

Two new MoogDb functions were added:

  • findMaintenanceWindows(filter, limit=100) - To find any maintenance windows. The arguments are:
    • filter A filter string (Something like: starttime > xxxx AND name matches yyy)
    • limit The maximal number of results to get back. (100 by default)
  • deleteMaintenanceWindows(filter, limit = 100) - To delete a bulk of maintenance windows. The arguments are:
    • filter A filter string (Something like: starttime > xxxx AND name matches yyy)
    • limit The maximal number of results to get back. (100 by default)
MOOG-6875

Update Default Cookbook / Recipes

The cookbook/recipes within each Integration/Solution Pack have been removed. Additionally, the 'Default Cookbook' recipes will now:

  • have an additional clustering by agent (100%)
  • no longer have the exclusion filter containing "agent = "DEMO_MAGIC"
MOOG-6910

A backup login mechanism has been added so if SAML login is unavailable then a DB login can be used. The changes are as follows:

  • If only SAML is configured then AIOps works as normal with no intermediate login screen
  • If both SAML and DB are configured then the login screen offers the choice between either SAML or DB (if SAML isn't working)

MOOG-6925

Improved JSON validation and SQL-like filter

The following moogdb module functions and graze endpoints now support an SQL-like query/filter as well as the JSON-formatted version:

  • getAlertIds
  • getSituationIds
  • createMaintenanceWindow
  • deleteMaintenanceWindow
  • findMaintenanceWindows

The validation used on each filter passed in has also been improved.

MOOG-6937

Improvements have been made to the moog_indexer/ElasticSearch indexing performance for alerts.

This change will require a full re-index of ElasticSearch. Please see the upgrade document for details.

MOOG-6945

Validate epoch for createMaintenanceWindow epoch via Graze

Additional validation has been added to the createMaintenanceWindow via the Graze API.

The duration must now be between 1 second and 5 years and the start time of the window may be up to 5 years in the future.

MOOG-6996

If any errors are detected in the Maintenance Window Manager dialog they will now remain onscreen rather than appearing for only a short period of time.

MOOG-7001

Remove unnecessary url validation on link definitions

In previous versions Link Definitions required a static URL in the pattern http(s)://example.com. This restriction has been lifted. This allows the link URL to be entirely built from Alert or Situation data. This provides extra flexibility when configuring in context launches from Moogsoft AIOps.

MOOG-7003

Custom Info display improvements

The custom_info display has been updated so data is now shown within an organised page tree. Previously this displayed data in raw JSON.

MOOG-7008

Maintenance windows are now sorted by default in ascending order by start time 

MOOG-7030

Two files have been added to the list of validated files that tomcat_install_validator.sh utility checks. These are $APPSERVER_HOME/conf/server.conf and $APPSERVER_HOME/conf/context.conf

MOOG-7048

The moog_indexer will now only support one indexing task to occur at any time unless one task targets alerts or situations specifically in which case another task may be started to target the other type specifically.
If the moog_indexer is running with the -f flag (or without the -f, -s, or -a flags) then it will be indexing both alerts and situations. During this time attempts to start another run of the moog_indexer will be denied (using any parameters).

MOOG-7110

AlertBuilder's Moobot's newEvent function can now return true or false to indicate successful Alert creation

When an AlertBuilder's Moobot processes Events from a REST LAM which has it's rest_response_mode value set to "event_processed", the newEvent function can return false to let the LAM know that it failed to process the Event, this in turn is relayed back to the client that sent the Event, who can choose to action on this feedback (i.e. attempt to re-send the Event to the REST LAM).

This improvement is backwards compatible, i.e. not returning a boolean will not cause an issue, it will be assumed that Event was successfully assimilated into an Alert.

MOOG-7122

INT-2210 : Updated all definition and configuration files for all the LAMs based on Event/Alert best practices and changes after integration testing

INT-1759 : The Dynatrace APM LAM has been improved to better parse hostname/IPs and provide validation on port numbers

INT-1024 : SSL support has been added for Zenoss LAM.

INT-1664 : The REST LAM now accepts JSON, XML & YAML data types, the LAM will auto-detect the data type based on the "Content-Type" value found in the request Header.

The following "Content-Type" formats are supported:

  • application/json
  • application/xml
  • application/x-yaml
  • text/xml

INT-2307 : Improved default retry attempts and intervals for polling LAMs. 
All Integrations no longer have their own Cookbook's and recipes, instead the default Cookbook has amended to match based on Agent. 
See  MOOG-6875 .

INT-1484 : An Advanced SCOM Connector is now available with HA functionality. See SCOM LAM for differences between the Basic & Advanced SCOM Connector. INT- 2502 fixed an issue with timezones in the SCOM Connector.

INT-2292 : The rest_client_lam's SSL configuration within the 'monitor' section has been corrected to include only relevant fields to enable SSL communication to the intended REST endpoint.

INT-2424 : The default configuration for the Netcool and Socket LAM were using the same port. Netcool's default port has been changed to 8412 (Socket LAM's default port is 8411)

INT-2444 : AWS CloudWatch Integration now auto selects active regions, simplifies the setup of log groups, allows login credentials that are delegate based and also provide timeout configuration.

INT-2804 : REST Client LAM now allows you to perform a request without specifying any query parameters. This was not possible in the 6.1.0 release.

INT-2805: The preClientSend and modifyResponse functionality that was added to the REST Client LAM in 6.1.0 is now optional.

INT-1767 : The Socket LAM now supports the UDP protocol, in SERVER Mode only.

INT-2423 : Outbound REST LAMs (i.e. those querying an external client) now have a timeout configuration which will timeout the request after x seconds (default is 120 seconds).

MOOG-7141

Auto Close enabled by default

Auto Close is now enabled by default for Alerts and Situations.
This default configuration will be only available for a first time installation. Alerts and Situations will be closed after one day of inactivity.

MOOG-7191

Change to AIOps tagline

The tagline for Moogsoft AIOps has been changed to 'Artificial Intelligence for Modern IT Ops and DevOps'. This followed Gartner's decision to redefine the product category.

MOOG-7244

Server information disclosure

The version of nginx used is no longer reported by nginx in the HTTP response headers.

MOOG-7141

Auto Close enabled by default

Auto Close is now enabled by default for Alerts and Situations.
This default configuration will be only available for a first time installation. Alerts and Situations will be closed after one day of inactivity.

MOOG-7191

Change to AIOps tagline

The tagline for Moogsoft AIOps has been changed to 'Artificial Intelligence for Modern IT Ops and DevOps'. This followed Gartner's decision to redefine the product category.

MOOG-7244

Server information disclosure

The version of nginx used is no longer reported by nginx in the HTTP response headers.


Bug Fixes

The following bug fixes have been added as part of this release:

KeyRelease Note
MOOG-5651

The mysql_install_validator now ignores GTID differences (used in Galera clusters for example).

MOOG-5979

An inconsistency with the naming of the Situation ID parameter in the Graze API has been fixed.

  • createSituation - now returns sitn_id
  • getActiveSituationIds - now returns sitn_ids
  • getSituationDetails - now returns sitn_id
  • getTeamSituationIds - now returns sitn_ids
  • mergeSituations - now returns sitn_id
  • getSituationIds - now return sitn_ids
  • getAlertDetails - now returns active_sitn_list
MOOG-6025

The mysql_install_validator now ignores all database views when determining database schema differences.

MOOG-6202

An issue which meant that the numbers displayed alongside Situation and Alert filters were incorrect in the Left Hand panel of the UI has been fixed.

MOOG-6216

An issue which meant that the Situation or Alert list 'Row Striping' was not enabled for each type List has been fixed.

MOOG-6289

Search queries containing space characters will now require that both terms are in the search results rather than any individual one.

MOOG-6400

An issue which meant that the Integrations UI would not display properly after immediately uninstalling a newly-added integration has been fixed. 

MOOG-6430

Fixed an issue where text fields and custom_info were not escaping HTML correctly.

MOOG-6485

The 'Set Default' button at the bottom of the Situation and Alert Filter screens was no longer required so was removed.

MOOG-6658

An issue that could deadlock the AlertBuilder Moolet, when using the event_processed handling modes in the REST LAM, has been resolved.

MOOG-6694

Some UI column widths have been adjusted so that the text/ordering arrows are no longer cut off.

MOOG-6709

Fixed issue where a user with manage_maint permission could not delete a maintenance window with the delete button from within the edit window.

MOOG-6740

The moogdb function setCustomInfoValue will now store number types in the correct format.

MOOG-6742

An issue which meant that Cookbook Trigger Filters would not be processed in the right order of operators has been fixed.

MOOG-6743

Fixed an issue where the UI display would break if a custom info field was trying to access a key of a null value in the custom_info object (for example if some of the alerts contained a parent key which was null).

MOOG-6745

Attempting to navigate to a specific Situation (for example) while logged out will now redirect the user to the page originally requested once login is complete.

MOOG-6757

An issue where responding to the sending client in the rest_lam when handling multiple events within a single payload has been fixed, it failed to respond to the sending client in some cases of high concurrency. This bug did not affect events being received into Moogsoft AIOps.

MOOG-6767

Fix to resolve an issue with incorrect Summary numbers being shown when a user does not belong to a team and is in Private Teams mode.

MOOG-6769

An issue where "regexp_subgroups" in the socket or logfile LAM was extracting a partial event, rather than waiting for the next buffer of data to fulfil a full, expected event, has been fixed.

MOOG-6783

The command line utility for installing integrations (via moog_init_ui.sh -x) now uses the media folder as configured in servlets.conf, under moogsvr/cache_root.

MOOG-6802

Fixed an issue where configurable requestTimeout in web.conf file was not respected in the Workbench.

MOOG-6816

An issue which meant that the logrotate cronjob would not complete successfully under RHEL7/CentOS7 has been fixed.

MOOG-6824

Missing function call added to the moog_init_search.sh script to ensure necessary environment variables are included.

MOOG-6832

An issue which meant that the socket_lam stopped processing events when a certain error condition was hit has been fixed. The LAM will now continue processing if such an error occurs and will log a message at WARN level to inform a system administrator.

MOOG-6836

The advanced filter in the maintenance window now accepts custom info.

Note that there is no validation for custom info filters.

MOOG-6854

The following MoogDb endpoints now return a numeric Id in a JSON Map instead of a boolean:

  • createMaintenanceWindow
  • createUser
  • createTeam
MOOG-6863

When creating or editing Maintenance Mode Windows, the External ID field will now accept string values in the basic filter and use the default string operator "matches".

MOOG-6866

The last_state_change time of a situation is now updated when the Situation's services or processes are changed.

MOOG-6889

An issue that resulted in some timestamps appearing in the UI with a future date e.g. "in a few seconds" has been fixed. After this fix, these times will be displayed as "a few seconds ago".

MOOG-6944

Fixed an issue where the UI session timeout was handled incorrectly and was not redirecting to login page automatically.

MOOG-6950

Solarwinds/REST Client LAM - no timeout on unresponsive poll request

An issue where the solarwinds_lam and the rest_client_lam didn't have a connection and request timeout caused the LAM to wait indefinitely, this has been fixed.

A default timeout has been added for 120 seconds, an optional configuration can be specified in the solarwinds and rest_client LAM:

#
# The timeout value in seconds, if not specified defaults to 120 seconds.
# This value will be used to timeout a connection, socket and request
#
#,timeout: 120
MOOG-6953

A warning which used to be logged when a Graze endpoint with valid SQL-Like filter was called has been removed.

MOOG-6956

The assignSituation and deassignSituation graze endpoints now return an empty response body when the operation is successful.

MOOG-6958

Attempting to delete the same maintenance window more than once via Graze will no longer generate an exception in catalina.out.

MOOG-6961

The last_access time related to the user session was updated by the websocket every minute and the session timeout was never happening.
This has been fixed and the user will now be logged out when the session reach the timeout, as expected

MOOG-6999

Previously it was possible for moog_farmd to shutdown moolets more than once, this has been corrected.

MOOG-7017

An additional validation has been done for the recurring period and the recurring period unit when creating a maintenance window from the moogDB module

MOOG-7021

An issue which meant that the MoogDb updateAlert() endpoint was generating an update where the custom_info was sent as a String instead of a Map has been fixed.

MOOG-7032

Fixed SQL error that was causing the PRC to not perform as expected under MySql database with sql_mode set to FULL_GROUP_BY_ONLY (not impacting MySql 5.6, unless the sql_mode were changed manually; default to MySql 5.7 database)

MOOG-7052

An issue which meant that a success message was displayed when a password change attempt was unsuccessful has been fixed.

MOOG-7061

The Services in the Summary page are now sorted alphabetically regardless of case.

MOOG-7065

A more user friendly error message is logged to moogfarmd.log if a moobot tries to create a duplicate team via the moogdb.createTeam method.

MOOG-7072

An issue which meant that the TeamsMgr moolet was generating very large messages which were not getting processed has been fixed.

MOOG-7088

Event fields are no longer supported when defining a Maintenance Window filter. Alert Fields are available instead.

MOOG-7091

An inconsistency with the Graze API for Sitn_Ids has been fixed. The Moogdb endpoints which have been modified are:

    • getTeamSituationIds - now returns sitn_ids
    • getActiveSituationIds - now returns sitn_ids
    • getSituationIds - now returns sitn_ids


MOOG-7134

The password field in the Server Tools dialog is now masked.

MOOG-7157

An issue which meant that certain special characters did not render correctly in the UI has been fixed.

MOOG-7162

Fixed the possibility of a Moolet being initialized more times than it was configured to, meaning doing more work than needed. This only affected certain types of specialized Moolets, like PRC.

MOOG-7203

An issue with configuring Moogsoft AIOps to authenticate with ADFS via SAML has been fixed.

Known Issues

Known issues with functionality in this release:

  • [MOOG-4616] - [SERVER] After rotation of the target logfile, the logfile_lam stops reading the target
  • [MOOG-5552] - [UI] Self monitoring tree-view occasional render issue
  • [MOOG-6734] - Hitting 'message size exceeded' on Sigs topic quite quickly in large scale environment due to message deltas
  • [MOOG-7426] - [PRC] Reset feedback in large Percona/Galera environment limited by wsrep_max_ws_rows and wsrep_max_ws_size settings
  • It has been observed that fresh installs of Chrome 60 can sometimes not correctly render the menus in AIOps. The workaround is to open then imediately close the Chrome Developer Tools window (View → Developer → Developer Tools). Alternatively, updating to the latest Chrome v61 seems to fix the issue.

Click here to download the PDF version of these release notes.




  • No labels