This is the second MVX: Performance release focused on improving replication as part of a MultiValue HA/DR strategy.  This release includes a new replication dashboard allowing users to quickly and easily perform replication monitoring tasks to assess, in real time, the health of replication activities. The replication dashboard includes details such as a statistical summary of multiple distributions and identifies the stalled LSN causing a subscription group to stop processing. A stalled LSN has been the number one replication-related support case our customers have submitted. This version of MVX: Performance provides resolution steps without users having to reinitialize servers. The dashboard also displays trend information such as pacing time behind and time to catch up.  In addition, v1.8 features three new replication events:

·        Replication disabled event: generated for one event per distribution if any groups are disabled.

·        Replication down event: generated if replication is down. It generates one event per distribution.

·        Replication up ("Replication Running") event: generated if the previous event is either Replication Disabled or Replication Suspended. It generates one event per distribution.

We updated the Replication Suspended event, first introduced in MVX: Performance 1.7.0, to be generated per replication group.

This release also includes:

·        Graceful handling of instance restarts and version-changes, for example, upgrading from UniVerse 11.3.4 to UniVerse 11.4.1.

·        A new Notification Only event alerts customers when a server is down and restarted. This feature was requested by our partners, alerting them to end users who might need assistance after a server goes down.

This version of MVX: Performance also gives users the ability to create their own custom events for monitoring application-level issues and errors that are not currently offered in the product. This feature took the Denver-regional prize during Rocket Build 2022.

Thirteen bug fixes are also provided in the release.  Please refer to the Release Notes for further details