Moogsoft Docs

Release Notes

Moogsoft AIOps v7.1.0 ESR

Moogsoft AIOps v7.1.0 is an Enterprise Stability Release that introduces a number of new features :

The key highlights include:

Cook-for Auto-Extension : Cookbook Recipe enhancement to help reduce the chances of duplicate Situations.

New integrations for Moogsoft Observe and Zabbix Webhook and extended UI configuration for several integrations.

New logging tool : L ogger has been replaced by Apache Log4j that allows for greater flexibility in logging con figuration.

Service Manager : A new command line utility allows you to control the services and processes to automatically restart when the Moogsoft AIOps system is rebooted.

Moolet configuration improvements : Moolets now have their own configuration files.

High Availability improvements : A change in the configuration of state persistence.

Two early access features : Situation Visualization enables you to view the source and origin of a Situation and Individual Performance Dashboards provide the means to view and compare new statistical data.

Moogsoft AIOps v7.1.0.7

The latest version of Moogsoft AIOps v7.1.0 is v7.1.0.7. This contains the following bug fixes:

  • INT-5324: Fixes an issue in some integrations which could not poll a non TLSv1.2 endpoint.
  • MOOG-13219: Situation updates in the Collaboration tab no longer disappear after a refresh.
  • MOOG-13233: A vulnerability within Tool ChatOps shortcuts has been fixed.

Refer to Moogsoft AIOps v7.1.0 Updates for details on all updates to this version.

Install & Upgrade

To perform a new Moogsoft AIOps installation without root user access, see Single Host Installation for Non-root .

To perform a new installation, see Pre-install RHEL 7/CentOS 7 or Pre-Install Moogsoft AIOps - Offline RPMs for an offline installation, then follow the instructions for one of the following:

Supported upgrade paths for this version are:

For more information see Moogsoft AIOps 7.1.0 Supported Environments .

Release Highlights

The feature and improvement highlights of the Moogsoft AIOps 7.1.0 release include:

Clustering Algorithms

Moogsoft AIOps 7.1.0 features the following algorithmic enhancement:

Cook For Auto-Extension

Cook for auto-extension is an enhancement to the "cook for" setting for a Cookbook Recipe that administrators and implementers can use to help reduce the chances of duplicate Situations.

By default a cook for time value in Cookbook is an estimated fixed length of time it takes before all related alerts for a Situation arrive after first alert detection. The cook for auto-extension feature detects if incoming alerts continue to correlate to a Situation beyond the "cook for" time value. If they do, it adds the alerts to an existing Situation rather than creating a duplicate.

The following new configuration properties enable a recipe to continue to correlate alerts beyond the cook_for time up to a configurable maximum duration :

  • cook_for_extension
  • max_cook_for

You can set these new properties in the Cookbook configuration file for a Cookbook and for individual Recipes.  See Configure a Cookbook Manually , Configure a Recipe Manually , and the Cookbook and Recipe Reference for more information.

Integrations and LAMs

Moogsoft AIOps 7.1.0 includes the following new integrations features:

New Integrations

  • Moogsoft Observe
  • Moogsoft Observe Polling
  • Zabbix Webhook

UI Configuration

The UI exposes additional configuration properties for the following integrations:

  • Apache Kafka
  • AWS CloudWatch
  • CA Spectrum
  • Datadog Polling
  • Dynatrace APM Polling
  • Email
  • EMC Smarts
  • HP NNMi
  • HP OMi
  • SolarWinds
  • Zabbix Polling
  • Zenoss

Additional Improvements

  • Polling integrations now create a Moogsoft AIOps critical alert when they fail to connect to the target system.
  • You can now define custom_info mapping in the UI and the LAM configuration files. This allows for a hierarchical custom_info structure.
  • REST-based LAMs now support static basic auth.
  • Refactored Syslog LAM.
  • The ServiceNow integration installation and configuration procedures have changed.

System Management

Moogsoft AIOps 7.1.0 has the following improvements for system management:

Logger

The Logger component has been replaced by Apache Log4j. This allows for greater flexibility in logging configuration and enables log levels to be dynamically changed while components are running.

Changes included as part of introducing Log4j are:

  • The default log levels for all utilities and components of Moogsoft AIOps are now: WARN|INFO|DEBUG|TRACE . The log levels FATAL and ALL have been removed.
  • All processes started from the command line now default to INFO apart from Moogfarmd which defaults to WARN but has special handling to always show some high priority INFO messages. These include: health logging, merge and resolve statistics, HA status changes, connection failover messages and Housekeeper tasks.
  • Log configuration files are now located at $MOOGSOFT_HOME/config/logging/ . See to the Log4j documentation for available configuration options. You can also refer to Log Configuration File Examples .

Warning

Log level configurations that were part of $MOOGSOFT_HOME/config/ servlets.conf and $MOOGSOFT_HOME/config/moog_farmd.conf have been removed.

Log rotation, previously configured in $MOOGSOFT_HOME/config/system.conf , is now configured in each component or servlet's individual log configuration file: $MOOGSOFT_HOME/config/logging/<component_log_file_name>.log.json

See Configure Logging for more details.

Service Manager

You can control the services and associated processes you want to keep alive when the system is rebooted using the new Service Manager utility.

See Configure Services to Restart for more details.

Configuration Improvements

The Moogfarmd configuration file has been refactored into separate files, so now each Moolet has its own configuration file by default.

The new Moolet config files can be found in $MOOGSOFT_HOME/config/moolets and follow the naming convention " <moolet_name>.conf" . For example: alert_builder.conf, cookbook.conf, indexer.conf etc.

The shortened Moogfarmd configuration file can still be found at $MOOGSOFT_HOME/config/moog_farmd.conf . You can reference additional Moolet configuration files in moog_farmd.conf using the 'moolets' array and an 'include' line. The array features all of the core Moolet configuration files by default:

moolets : [
	{
		include : "scheduler.conf"
	},
	{
		include : "sigaliser.conf"
	}
]

HA Improvements

The persist_state configuration property has been removed from the configuration files for all Moolets. Instead this option is enabled by default for all Moolets including Cookbooks configured via the UI in the event of a failover.

You can disable persist_state for all Moolets in the failover section of $MOOGSOFT_HOME/config/system.conf .

Moogfarmd Health Logging

Moogfarmd health logging now includes Moolet message queue usage and capacity.

Early Access Features

There are two Early Access features that you can trial from this release. These are disabled by default. To enable them go to Settings > Labs in the Moogsoft AIOps UI.

Situation Visualization

The Situation Room has a new Visualize tab that enables you to view the source and origin of a Situation. For example, you can see whether a Situation is the result of a Cookbook Recipe, a manual merge or when two Situations have been merged together.

Graze API includes a new endpoint getSituationVisualization. When you provide the Situation ID, it returns the source and origin of the Situation. For example, if a Cookbook Recipe created the Situation, getSituationVisualization returns the details of the Cookbook and Recipe that created it.

Individual Performance Dashboards

There are new Stats API endpoints and two new dashboards in the 7.1.0 version of Moogsoft AIOps for Grafana plugin:

  • Individual Stats Overview : The dashboard allows you to view and compare statistics for multiple Moogsoft AIOps users. By default Moogsoft AIOps collects statistical data for this dashboard for all users with the operator role. You can add or remove the 'collect_insights' permission to other roles to include or exclude other users in the dashboard.
  • Individual User Deep Dive : The Individual User Deep Dive dashboard provides an in-depth summary of different performance metrics for a single user. By default Moogsoft AIOps collects statistical data for this dashboard for all users with the operator role. You can add or remove the 'collect_insights' permission to other roles to include or exclude other users in the dashboard.
  • New Stats API endpoints : You can expose user activity using the following endpoints:

    • getAlertsMarkedPRCPerUserStats
    • getAcknowledgedSituationsPerUserStats
    • getAssignedSituationsPerUserStats
    • getChatOpsToolExecutedPerUserStats
    • getClosedSituationsPerUserStats
    • getCommentCountPerUserStats
    • getInvitationsReceivedPerUserStats

    • getMTTAPerUserStats
    • getMTTRPerUserStats
    • getOpenSituationsPerUserStats
    • getRatedSituationsPerUserStats
    • getReassignedSituationsPerUserStats
    • getResolvedSituationsPerUserStats

    • getViewedSituationsPerUserStats
    • getWorkedSituationsPerUserStats

    See User Endpoints in the Stats API documentation for more information.

New Features

Key Release Note
MOOG-9777

Individual Performance Insights data can now be collected. In the UI go to Settings > Labs > Configure to enable and disable it. This is an Early Access feature. Do not enable it on production systems.

MOOG-10783

The Situation Room has a new Visualize tab that enables you to view the source and origin of a Situation. This is an Early Access feature. Do not enable it on production systems. A new GrazeAPI endpoint getSituationVisualization can be used to return the same details.

MOOG-10788

A new Cookbook feature dynamically extends the cook_for time on a per-recipe or per-Cookbook basis. See the Cookbook and Recipe Reference for more information.

MOOG-10834 MOOG-10840 MOOG-11093

New user permissions have been added:

  • collab_read: View content added by other users on the Collaborate tab within Team and Situation Rooms.
  • collab_write: Add content to the Collaborate tab within Team and Situation Rooms.
  • sig_resolve: Resolves Situations. Granted by default to the Administrator, Manager, Operator and Super User roles for new installation and upgrade, and to any other roles with the sig_modify permission.
  • view_summary: Allows a user to view the summary page. By default every role has this permission.

You will need to add the collab_read and collab_write permissions to any custom roles to enable user access to the Collaborate tab.

MOOG-11121

A new Service Manager command line utility allows you to control the services and associated processes you want to restart automatically when the system is rebooted.

MOOG-11435

A new Graze endpoint getSimilarSituations retrieves similar Situations for a given Situation ID. See the Graze API Reference for more details.

MOOG-11436

A new Graze endpoint getSimilarSituationIds retrieves a list of similar Situation IDs for a given Situation ID. See the Graze API Reference for more details.

MOOG-11563

Grafana contains two new individual performance dashboards:

  • Individual User Deep Dive: Provides a summary of different metrics for a selected single user.
  • Individual User Stats Overview: Provides a performance comparison of metrics for multiple users.
INT-4210

A new Zabbix Webhook integration has been added. See Zabbix for more information.

INT-4524

New Moogsoft Observe and Observe Polling integrations have been added. See Moogsoft Observe for more information.

INT-4628

Moogsoft AIOps now creates a critical alert with class 'Failed Connection Attempt' when the following polling integrations and LAMs fail to connect to the target system. Details are also written to the process log.

  • Dynatrace APM Polling
  • Email
  • HP NNMi
  • HP OMi Polling
  • JDBC
  • REST Client
  • SevOne
  • VMware vCenter
  • VMware vRealize Log Insight
  • VMware vSphere
  • Zabbix Polling
  • Zenoss

If the integration or LAM polls successfully on the next attempt, the alert is cleared. If the integration or LAM is restarted to resolve the connection issue the alert is not cleared and must be handled manually. See Logging for more information.

Improvements

Key Release Note
MOOG-11839

Individual Performance Insights & Visualize are early access features that can be enabled in the Labs section of the UI. Do not enable these features in production environments for now.

MOOG-11529

When SAML is configured to map IdP role and team attributes to roles and teams that do not exist in MoogDb, Apache Tomcat now logs an error message.

MOOG-11519

The Events Analyser defaults have changed so that it now analyzes event data that has been received since it was last run, or over the last two weeks, whichever is the latest.

MOOG-11302

The new Graze endpoint getSituationPinpoint displays details about the origin of a Situation. See the Graze API reference for more information.

MOOG-11245

The Anon user has been disabled and can no longer log into the UI.

MOOG-11244

The Collaborate tab in the UI now displays a spinner icon when waiting for a network request.

MOOG-11196

Maintenance windows now support filtering on custom_info in alerts.

MOOG-11183

The persist_state property has been removed from all Moolet configuration files. Persistence is enabled by default for all Moolets including Cookbook in the event of failover. It can be disabled for all Moolets in $MOOGSOFT_HOME/config/system.conf .

UI-based Cookbooks can now persist as well, which was not the case prior to this release. UI Cookbooks are now correctly sharing memory state between instances of Moogfarmd. If you predominantly use UI-based Cookbooks you are likely to see an increase in CPU and Memory in the Moogfarmd processes as a result.

MOOG-11152

The feature for alerts handover between overlapping maintenance windows is now enabled by default.

MOOG-11131

The target returned for Individual Performance statistics is now more explicit. It includes of the name of the statistics and the affected user.

MOOG-11122

Logging has been added to the automated service restart scripts service_manager and process_keepalive.

MOOG-10871

The Graze API call getSystemStatus now includes additional health information for processes with an internal pool. See the Graze API reference for more information.

MOOG-10868

Queues in Moogfarmd memory now have an optional size limit. You can configure Moogfarmd and its component Moolets to not consume messages from RabbitMQ until they have the capacity to process them.

Warning

Do not change these properties unless advised to do so by Moogsoft Support. Changes can seriously impact processing performance if configured incorrectly.

The relevant properties in the Moogfarmd configuration file are as follows:

  • bus_thread_pool_queue_limit : Size of the message queue. Default to 0 (unlimited).
  • moolet_queue_size_limit : Size of the message queue for all Moolets. Defaults to 0 (unlimited).

To modify the message queue size for a specific Moolet, configure the moolet_queue_size_limit property in the Moolet's configuration file. Queue states are reported in the Moogfarmd health log and in the getSystemStatus Graze API call.

Moogfarmd health logging now includes Moolet message queue usage and capacity in the message_queues block. In previous releases the format of messages_queues was as follows:

"message_queues":
{"AlertBuilder":0,"Cookbook":0,"Housekeeper":0,"Indexer":0,"bus_thread_pool":0,"SituationMgr":0}

The new format of message_queues is now:

"message_queues":
{"AlertBuilder":"0/-","Cookbook":"0/-","Housekeeper":"0/-","Indexer":"0/-","bus_thread_pool":"0/-","SituationMgr":"0/-"}

The values are now strings rather than integers and "-" represents an unlimited queue. A numeric queue limit value can also be used.

MOOG-10833

Grafana now contains more explicit dashboard titles.

MOOG-10814

When a Situation is manually created the details are now included in the Apache Tomcat log and in the Situation's custom_info.

MOOG-10640

The keepalive process now supports systemd and process_cntl respectively for RPM and non-root installs. RPM and non-root deployments have improved service and process restart behavior. Restarts are controlled via a cron job running once per minute in clean installations (if it was installed with the -k option in the initialization script). It reads the configuration file $MOOGSOFT_HOME/config/keep_procs_alive.conf to determine which services to restart. A new Service Manager utility can be used to enable and disable services for automatic restart.

MOOG-10545

There is now a separate configuration file for each Moolet, located in $MOOGSOFT_HOME/config/moolets . The Moogfarmd configuration file calls these files using the 'Include' keyword. Configuration files in use prior to this release will continue to work, however we recommended switching to the new format. See Moogfarmd and Moolets for more information.

MOOG-10425

The display options for Situation Topology have been simplified. Legend information has been removed and the legend no longer displays scroll bars in Internet Explorer.

MOOG-10297

The RabbitMQ configuration file now ships with the cluster_partition_handling property set to autoheal. This allows a RabbitMQ cluster to automatically handle a network partition and will restart required RabbitMQ nodes to achieve this. Without this setting, a RabbitMQ cluster that experiences a network partition will remain partitioned (until the problematic node is restarted) which can lead to incorrect or lost data for Moogsoft AIOps components.

Running moog_init_mooms.sh (for the Message Bus) now sets ha-all policy on all queues ending with ".HA". This allows RabbitMQ to synchronize the queue across the cluster. Without this setting Moogsoft AIOps will not work correctly in distributed HA environment.

MOOG-10254

The Logger component has been replaced by Apache Log4j. This allows for greater flexibility in logging configuration and enables log levels to be dynamically changed while components are running. See Configure Logging for more information.

MOOG-9581

Apache Tomcat no longer reveals the server information on error pages.

INT-4765

REST-based integrations can now be configured to authenticate with a specified username and password.

INT-4754

In the SolarWinds integration, the overlap identity fields can now include EventTypeName and Message.

INT-4721

Integration names can no longer be modified after an integration has been installed.

INT-4717

The Zenoss integration UI has been extended. You can now configure multiple targets, specify event states and severities to poll and modify the timing properties.

INT-4715

The Zabbix Polling integration UI has been extended. You can now configure multiple targets, specify the types of events to poll and modify the timing properties.

INT-4714

The Apache Kafka integration UI has been extended. You can now specify the group ID and multiple topics.

INT-4713

The Datadog Polling integration UI has been extended. You can now specify multiple targets and modify the timing properties.

INT-4709

The HP OMi integration UI has been extended. You can now specify multiple targets and modify the timing properties.

INT-4708

The Email integration UI has been extended. You can now specify multiple targets and filters and modify the timing properties.

INT-4707

The CA Spectrum integration UI has been extended. You can now specify multiple targets and modify the timing properties.

INT-4706

The EMC Smarts integration UI has been extended. You can now specify brokers and topics.

INT-4705

The AWS CloudWatch integration UI has been extended. You can now specify a filter and modify the timing properties.

INT-4678

You can now define custom_info mapping in LAM configuration files. This allows you to configure a hierarchical structure. See Data Parsing for more information and an example.

INT-4639

CA Spectrum LAM can now utilise a proxy.

INT-4631

Logging in the Email integration and LAM has been improved, including the addition of a javamail_debug property to enable JavaMail debug mode.

INT-4592

The following integrations and LAMs now include the target name and target URL in the event payload:

  • REST Client
  • SolarWinds
  • VMware vCenter
  • VMware vSphere
  • Zabbix Polling

The target name and URL are written to custom_info.eventDetails.moog_target_name and custom_info.eventDetails.moog_target_url. They are also available in the LAMbot functions and can be disabled if necessary.

INT-4481

The HP NNMi integration UI has been extended. You can now specify multiple targets and filters and modify the timing properties.

INT-4478

The Dynatrace APM Polling integration UI has been extended. You can now specify multiple targets and modify the timing properties.

INT-4469

The SolarWinds integration UI has been extended. You can now specify multiple targets and modify the timing properties.

INT-4446

The CA Spectrum LAM now follows the standard configuration style for polling multiple servers.

INT-4421

REST Client LAM now supports static JWT tokens for authentication.

INT-4414

UI Enrichment is now case insensitive when performing lookups.

INT-4399

Syslog LAM has been refactored to handle common syslog formats, such as RFC-3164 and RFC-5424, more effectively.

INT-4372

Severity mapping in the CA Spectrum integration has been updated.

INT-4370

The header information on UI integrations is now affixed to the top of the screen when scrolling down.

INT-4246

Users now create their own user names and passwords.

INT-4226

The scripts that enable Nagios to send events to the Nagios LAM (send-host-event and send-service-event) now have retry functionality and can retry up to 5 times with a 5 second delay between attempts.

INT-3831

In the integrations UI, data mapping now accepts JSON lists and object values for custom_info.

DOCS-1239 The ServiceNow integration installation and configuration procedures have changed.

Bug Fixes

Key Release Note
MOOG-10452

A dependency for moogsoft-common has been added to the moogsoft-mooms package.

MOOG-10484

Invalid links under Workbench in the UI now redirect to the summary screen.

MOOG-10763

The Stats API endpoint getStats now lists endpoints in alphabetical order with improved descriptions.

MOOG-10802

A Graze API authentication problem has been fixed.

MOOG-10816

The PRC trigger file prc_trigger is now located in $MOOGSOFT_HOME/bin/utils and included in dev-utils RPMs.

MOOG-10890

The closure of alerts in an open Situation was causing some unexpected behavior, which is now resolved.

MOOG-10911

Alerts which were part of an expired maintenance window are now transferred to the next overlapping maintenance window, if window_handoff is enabled in the Moogfarmd configuration. By default window_handoff is disabled and alerts are not transferred.

MOOG-10934

The Process Control utility now waits until the stop request is successful when performing a restart.

MOOG-10951

The Stats API endpoints getReoccurringSituationStats and getReoccurringSituationPerTeamStats now return the target string 'Reoccurring Situations'.

MOOG-10973

The Grafana dashboard Ops Insights no longer displays an incorrectly large value for the 'Situations by Status' and 'Situations by Severity' metrics in some circumstances.

MOOG-10989

A closed Situation can no longer create clusters in Cookbook in some circumstances.

MOOG-11018

The Grafana dashboard Noise Reduction no longer displays an incorrectly large value for the 'Alerts in New Situations' metric in some circumstances.

MOOG-11026

The correct SSL port has been added to the redirect in the non-SSL Nginx configuration.

MOOG-11153

The thread previously displayed in the Moogfarmd logs as [0:Housekeeper] now displays as [0:Housekeeper:Scheduled-Tasks] .

MOOG-11207

MTTA and MTTR Per User statistics now return a target string that correctly combines the usernames when multiple users are selected and the 'sum' aggregation type is used. The returned target string is now 'Mean Time to Acknowledge (MTTA) (User1/User2/User3)'.

MOOG-11227

Situation data is now saved to the persistence store when the process to create or update a Situation fails.

MOOG-11274

Lifespan management of bot modules is now more reliable and less prone to unexpected errors. The error "could not check out resource while closing down the pool" no longer appears.

MOOG-11279

A new Situation with closed alerts is no longer created in a high event rate scenario.

MOOG-11289

The help text for the following utilities now displays the correct details:

  • moog_remove_alert_custom_field
  • moog_fill_sitn_custom_fields
  • moog_remove_sitn_custom_field
MOOG-11346

New candidate Situations no longer override existing Situations on Cookbook failover in some scenarios.

MOOG-11380

The default SAML configuration in security.conf no longer overwrites existing Moogsoft AIOps users and assigned roles and teams.

MOOG-11474

A form previously accessible from /moogsvr/mooms has been removed and an error is returned instead if this URL is accessed. This removes a potential security threat.

MOOG-11523

The one_hop_topo table now contains only one instance of every edge in the Situation topology.

MOOG-11619

The failover mechanism now relies on RabbitMQ as well as MySQL and Moogfarmd. When automatic failover is enabled, Moogfarmd can now become active only when there is consensus between RabbitMQ and database failover mechanisms. This is to prevent scenarios where RabbitMQ or the database connection is not responding correctly, which can lead to an active-active scenario for Moogfarmd. Additionally, when auto failover is enabled, the process will immediately become passive on any RabbitMQ or database connectivity issues.

MOOG-11667

The process keepalive script is now added to crontab if the -k option is used in the initialization script during installation.

MOOG-11689

The initialization script now uses the Process Control utility to restart MySQL in non-root deployments. This resolves an issue preventing MySQL from restarting successfully.

MOOG-11695

Grafana Individual Insight statistics now display a user's full name instead of their username.

MOOG-11711

A potential deadlock in the Moogfarmd shutdown process has been removed.

MOOG-11737

The Situation Topology no longer fails to render in some circumstances.

MOOG-11769

The error "could not check out resource while closing down the pool" no longer appears on Moolet restart.

MOOG-11841

The India support phone number is no longer in use and has been removed from the UI.

INT-3837

Cherwell and Remedy integrations now have authentication validators in their configuration.

INT-3953

The New Relic Polling integration now retrieves events of type 'violations'.

INT-4106

The HP OMi integration now retrieves closed events.

INT-4140

REST-based integrations now accept requests with the header "Expect: 100-Continue". This improves performance for large payloads.

INT-4178

The SolarWinds integration and REST Client LAM now support the same retry functionality as the other polling integrations.

INT-4282

The event state in the Zenoss LAM is now configurable. Clear events are now polled by default.

INT-4326

Creating and manipulating monitoring integrations in the UI no longer interacts with Moogfarmd.

INT-4486

The JDBC LAM's error message relating to data retrieval failure has been improved.

INT-4494

xMatters communication v4.1 has been released, with corrections to the wording in the email sent from xMatters when a group or user is engaged.

INT-4495

When a ticket is closed in Jira Software or Jira ServiceDesk the corresponding Situation in Moogsoft AIOps is now correctly closed.

INT-4500

The documentation link in the HP OMi integration UI has been corrected.

INT-4501

An issue that caused a 'null.state' LAM file to be packaged in the distribution has been fixed.

INT-4504

The custom payload in the Dynatrace Notification integration has been corrected.

INT-4514

An error logging problem has been corrected in RabbitMQ and the EMC Smarts LAM.

INT-4554

A Remedy integration error that created a continuous loop has been resolved.

INT-4575

The moogsoft-integrations RPM now contains the necessary files to run LAMs standalone. This is useful for distributed deployments. Note that system.conf is still required.

INT-4701

State files are no longer produced or read by integrations and LAMs.

INT-4753

Validation has been improved in the xMatters integration. The 'Username' property has been renamed to 'Web Login' for improved clarity.

INT-4797

Integrations created prior to Moogsoft AIOps 7.1.0 will function but cannot be edited. To update the details, delete the old integration and create a new one.

Documentation Improvements

In addition to new feature coverage, the Moogsoft AIOps 7.1.0 documentation contains the following improvements:

Deprecation Notices

Known Issues

Key Release Note
MOOG-11838 RabbitMQ allow plain text authentication methods. Moogsoft recommends that you configure RabbitMQ in a secure manner unless absolutely required. See RabbitMQ documentation for more information.
MOOG-12389 In certain conditions, Cookbook adds closed alerts to new Situations. When a Situation containing a single alert is closed and Cookbook creates a new Situation within the same cook_for time, it adds the closed alert from the previous Situation to the new Situation.

Release Date

2019-01-25

For information on previous Enterprise Stability Releases see Moogsoft AIOps Releases .