What's new in IBM Cloud Pak for Watson AIOps 4.1.0

Get a quick overview of what is new with IBM Cloud Pak® for Watson AIOps.

IBM Cloud Pak for Watson AIOps 4.1.0 includes new and updated features for connecting with other applications and services, viewing and resolving incidents and alerts, visualizing topologies, creating policies, and more.

The IBM Cloud Pak for Watson AIOps 4.1.0 also introduces changes and fixes to address known security vulnerabilities. These additions help to ensure that your IBM Cloud Pak for Watson AIOps installation is kept up-to-date and secure and can better meet your business needs.

Important: The AI Manager and Event Manager capabilities are replaced with a single AIOps capability within IBM Cloud Pak for Watson AIOps. The only references to AI Manager are related to the AI Manager Operator and instance in Red Hat OpenShift.

The following new features and changes are introduced with this IBM Cloud Pak offering:

Install and upgrade

  • Support is added for Red Hat® OpenShift® Container Platform 4.12 for upgraded deployments of IBM Cloud Pak for Watson AIOps. This was previously only supported for new deployments of IBM Cloud Pak for Watson AIOps. Learn more
  • You can now specify whether you want collections of topology resource groups to be referred to as applications or services. Learn more
  • IBM Cloud Pak for Watson AIOps can now optionally use a FIPS compliant custom cluster certificate configured in Red Hat® OpenShift® Container Platform. Learn more. Alternatively, you can optionally create your own custom certificate. Learn more
  • The AI Model Management user interface no longer requires a persistent volume claim (PVC) to maintain the training job state, and you can delete the PVC for training job state data that is no longer required. For more information see, Deleting a persistent volume claim.

Defining connections and integrations

Managing applications (services) and viewing topologies

  • You can now configure the UI to label your groups-of-groups collections of resources as either 'applications' or 'services', depending on which term more accurately describes your situation. The system default is 'application', which is also used in the documentation. For more information, see the following Tip.

  • You can now display topology data in a tabular format, from where you can access additional resource details. For more information, see Tabular view

  • You can filter Search results by defining filter conditions, which you can save for future use by specified users. See Searching and filtering.

  • You can specify additional properties to be available when filter conditions are defined. For more information, see Topology search: Add additional properties for filtering.

  • You can change the default hop type. For more information, see Topology rendering: Default hop type for topology viewer.

  • Use keywords to configure probable cause. For more information, see About probable cause ranking and Configuring probable cause.

Resolving incidents and alerts

  • The UI terminology is changed so that stories are now labelled incidents. Also, similar incidents, such as from a ServiceNow integration, are called similar tickets.

  • In the Alert Viewer, you can now create bespoke filter conditions using alert properties. There is also improved access control around your saved filters. Searching and filtering alerts.

  • Explainability drill-down for temporal correlation and seasonal alerts. The temporal details page shows the alerts that make up a temporal group, together with all of the historical instances of the group. The seasonality details page provides a calendar view of all of the historical alerts that contributed to the selected seasonal alert. For more information, see Displaying temporal correlation and Displaying alert seasonality.

  • You can now use quick filters as a fast way of displaying alerts that match a selected criteria. For example, you can quickly display only those alerts that occurred at the same time as, or before, a selected alert. A quick filter is applied via the right-click context menu. For more information, see Creating quick filters.

  • Personalize the arrangement of right-click menu items in the Alert Viewer. The arrangement is only visible to the user customizing the menu. That is, each user can define how their own menu looks. For more information, see Working with alerts.

  • You can now include additional metrics (up to another 3 KPIs) on the Metric anomaly details chart when you view the details from the Alert Viewer. For more information, see:

Automating processes (Policies, Runbooks, Actions)

  • Manage the alert seasonality and temporal grouping policies that are created by AI analytics. Once draft policies are reviewed they can be deployed or moved to archived if unwanted. For more information, see Draft and archived policies.

  • You can now drill-down into the Temporal and Seasonality policy detail pages for more explainability about temporal correlation and seasonality policies. For more information, see Temporal policy details and Seasonality policy details.

  • Create a Cloud Pak for Watson AIOps policy that invokes an IBM Tivoli Netcool/Impact policy, via the IBM Tivoli Netcool/Impact connector. By default, IBM Tivoli Netcool/Impact policies are invoked without input or transformation. Editing options are available in the IBM Tivoli Netcool/Impact policy template. For more information, see Invoke an IBM Tivoli Netcool/Impact policy.

  • New automation action type for Client-side actions. Client-side actions provide a mechanism to launch out from the Cloud Pak for Watson AIOps user interface in the user's browser to any third-party website. For more information, see Creating Client-side actions.

  • New automation action type for Predefined actions. Predefined actions perform some standard changes on alerts, such as acknowledging the alert, assigning the alert, or modifying the severity of the alert. For more information, see Predefined actions.


  • New troubleshooting topic that describes how to halt a single Cassandra node for maintenance. See the following topic for more information: Halt Cassandra node for maintenance

Non-production (tech preview)

IBM Cloud Pak for Watson AIOps includes the following components and features for non-production use as a technology preview:

  • Application disruption costs (in AIOps insights)
  • Golden signal incident prioritization
  • Feedback learning for statistical baseline log anomaly detection
  • Log anomaly automated training data selection
  • Log anomaly model drift detection
  • Multi-zone high availability and disaster recovery (HADR)
  • Datadog observer and integration probe for data collection

For more information about these feature previews, see Non-production features (Technology preview).

Infrastructure Automation

Previously introduced features and changes

For more information about new features and changes that were introduced in previous versions of IBM Cloud Pak® for Watson AIOps, see: