New Features
Moogsoft Enterprise v8.0 contains the following new features.
Ticket | Release Note |
|---|---|
MOOG-14340 | You can now create multiple topologies, so different teams and technology domains can have their own physical and logical topological views. Moogsoft Enterprise can cluster alerts into Situations based on the topological relationships between the alerts. You can create topologies using the Topologies API and/or the Topology Loader utiilty. For details see Topology Overview. |
MOOG-14123 | Alert Analyzer (Entropy) enables you to visualize and understand the impact of entropy values in Moogsoft Enterprise and adjust them to effectively reduce operational noise. For details see Alert Analyzer Utility. |
MOOG-12004 | The Visualize feature is now GA. The Visualize tab in the Situation Room allows users to see details pertaining to the Cookbook and Recipe used to create the Situation. This includes a visual depiction of all of the Situations' alerts and their similarity to the reference alert. Provides a Situation list of all of the associated alerts. Administrators can also apply changes to the Cookbook and Recipe through Visualize. For details see Review and Adjust Clustering Settings with Situation Visualization. |
MOOG-13485 | Moogsoft Enterprise now enables audit logging of user sessions and authentication, authorization changes, and configuration changes. For details see Audit Logging. |
MOOG-14127 | We have added versioning for Cookbooks and Recipes. You can now view the change history and restore an earlier version of a Cookbook or Recipe. For details see Restore a Cookbook or Recipe. |
MOOG-15151 | You can now create a new Workflow Engine to trigger workflows based upon Situation Action messages. For details see Create a Situation Action Workflow Engine. |
MOOG-14896 | You can now invoke a specific Situation workflow or Alert workflow outside of the standard Moolet message processing chain. For details see Workflow Engine. |
MOOG-13524 | The Historic Data utility (splitter) is now always on in v8.0.0.x and can no longer be disabled. Configuration changes to the Historic Data utility are now made via the moog_db_split_configurer utility which replaces the moog_db_split_enabler utility. For details see Configure Historic Data Retention. |
MOOG-13524 | The active database, by default, now only retains two weeks' worth of event and snapshot data. The Historic Data utility (splitter) is responsible for enforcing this. Older event and snapshot data is retained in the historic database (subject to archiving). The retention period for active event and snapshot data can be configured using the moog_db_split_configurer utility. |
INT-5635 | The new PagerDuty integration enables bidirectional communication between Moogsoft Enterprise and PagerDuty. For details see PagerDuty. |
INT-5566 | The new Opsgenie integration enables bidirectional communication between Moogsoft Enterprise and Opsgenie. For details see Opsgenie. |
INT-5683 | The new Moogsoft Express Polling integration enables Moogsoft Enterprise to collect alert data from one or more Moogsoft Express systems. For details see Moogsoft Express Polling (DEPRECATED). |
INT-5685 | The new Moogsoft Express webhook posts data to when an alert occurs in Moogsoft Express. For details see Moogsoft Express Webhook (DEPRECATED). |
INT-5705 | The new AWS Flrelens integration enables you to route logs from ECS containers to Moogsoft Enterprise. For details see AWS FireLens. |
INT-4368 | On an integration’s data mapping screen, you can now specify the current time in agent mapping, view unmapped custom info fields and map them, map to a specified location in an array, map fields with default values, and unmap custom info fields. For details see Data Ingestion. |
INT-5550 | Brokers and UI integrations can now communicate via websockets instead of just on RabbitMQ. |
INT-5551 | Moogsoft Bridge is a new replacement and alternative to the Message Bus Cache LAM (mooms_cache_lam). It pushes events and messages from a local RabbitMQ cluster to the Message Bus, without requiring an inbound connection to the customers on-premise environment or local databases. |
INT-5816 | After upgrading integrations (RPM or Tarball) to v8.0, any UI integrations and brokers that were running on v7.3.x automatically update. Integrations that cannot be upgraded display as deprecated (xMatters, Dynatrace Synthetic). |