What's new in IBM Cloud Pak for AIOps 4.7.0

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

IBM Cloud Pak for AIOps leverages AI to streamline IT operations, increase uptime, improve efficiency, and reduce costs. The solution supports Operations teams to deliver optimum performance and assurance by:

  • Breaking down data silos
  • Providing real-time insights into IT systems
  • Augmenting incident management with AI
  • Automating incident resolution

With Version 4.7.0, IBM Cloud Pak for AIOps delivers improved capabilities and new features for deploying IBM Cloud Pak for AIOps, defining ticketing and metric integrations, and more.

Overall, the following new features and changes are introduced with this IBM Cloud Pak version:

Install and upgrade

Deployment on Red Hat® OpenShift® Container Platform The following new features are introduced for deployments of IBM Cloud Pak for AIOps on Red Hat OpenShift :

  • Red Hat OpenShift 4.16 support Support is added for Red Hat OpenShift 4.16 for new or upgraded deployments of IBM Cloud Pak for AIOps. Learn more

  • New catalogs and revised upgrade process IBM Cloud Pak for AIOps v4.7.0 uses the new catalogs ibm-aiops-catalog, ibm-cert-manager-operator-catalog and ibm-licensing-catalog instead of ibm-operator-catalog. This improves stability by fixing the IBM Cloud Pak for AIOps and dependent operators to specific versions. Existing online deployments that are upgrading to v4.7.0 are migrated to use the new catalogs as part of the upgrade process. Before v4.7.0, online deployments not pinned to a version automatically upgraded if a new patch became available in the subscribed to channel of the catalog ibm-operator-catalog. All IBM Cloud Pak for AIOps upgrades must now be manually initiated. Learn more

  • Multi-zone cluster rebalancing A procedure is provided to rebalance workloads for a deployment of IBM Cloud Pak for AIOps on a multi-zone Red Hat® OpenShift® Container Platform cluster. Learn more

  • ODF backup storage Red Hat® OpenShift® Data Foundation can now be used as the storage for an OADP backup of IBM Cloud Pak® for AIOps. Learn more

  • Postgres PVC adjustment There is a new procedure to increase the size of the Postgres PVC. Learn more.

  • MinIO PVC adjustment There is a new procedure to increase the size of the MinIO PVC. Learn more.

Deployment on Linux® Learn more Deployment of IBM Cloud Pak for AIOps on Linux is now a fully functional deployment option. This was previously a technology preview only feature in IBM Cloud Pak for AIOps 4.6.0 and 4.6.1. The following features are introduced to make deployment on Linux production-ready:

  • Increased platform support Support is added for Red Hat® Enterprise Linux® 8.10 and Ubuntu 24.04 Learn more

  • High availability deployment (IBM Cloud Pak for AIOps on Linux) Deployments now use three control plane nodes instead of one, to provide better stability and availability. All procedures are updated for this. Learn more

  • Backup and restore (IBM Cloud Pak for AIOps on Linux) is now supported. Learn more

  • Custom certificate usage (IBM Cloud Pak for AIOps on Linux) You can now configure your deployment to use a custom certificate, at installation time or postinstall

  • Custom sizing (IBM Cloud Pak for AIOps on Linux) Custom sizing your deployment is now supported. Learn more

  • Restarting the environment (IBM Cloud Pak for AIOps on Linux) A procedure to shutdown and restart the Linux cluster that IBM Cloud Pak for AIOps is installed on is now supported. Learn more

  • Local storage configuration (IBM Cloud Pak for AIOps on Linux) A procedure to configure dedicated disk and volumes before installing IBM Cloud Pak for AIOps is added. Learn more

  • Deployment status reporting (IBM Cloud Pak for AIOps on Linux) A new server status option is available for the aiopsctl tool that gives the status of all of the components of your deployment. Learn more

  • Adding a node (IBM Cloud Pak for AIOps on Linux) There are new procedures to add a worker node or control plane node to your deployment. Learn more: worker and control plane

  • Removing a node (IBM Cloud Pak for AIOps on Linux) There is a new procedure to remove a node from the IBM Cloud Pak for AIOps deployment, using a new cluster node down option for the aiopsctl tool Learn more

  • Recovery from node failure (IBM Cloud Pak for AIOps on Linux) There is a new procedure to delete a failed node and recover its workloads and storage to alternative nodes, using a new cluster delete-node option for the aiopsctl tool. Learn more

  • Resizing storage (IBM Cloud Pak for AIOps on Linux) A procedure for resizing local storage volumes is added. Learn more

  • Uninstall (IBM Cloud Pak for AIOps on Linux) There is a new more integrated procedure for the uninstallation of IBM Cloud Pak for AIOps on Linux. Learn more

Defining integrations (connections)

  • Jira integration: You can now integrate with Jira to enable connectivity to Jira tickets. This enables you to view the resolutions for Jira incidents within IBM Cloud Pak for AIOps based on the similar Jira tickets. For more information, see Creating Jira integrations.

    When the Jira integration is up and running, you can create a policy that opens an incident within Jira by selecting the integration from the Open a ticket area of your Promote alerts to an incident policies. See Steps 12 and 13 of Promote alerts to an incident.

  • Configure proxy and fetch SSL certificate for metric integrations: For creating connector integrations retrieving metric data, you can now select to fetch the SSL certificate or manually input the certificate to verify the SSL/TLS certificate for the REST service. You can also now define a proxy configuration when you are creating these metric integrations.

    The following integrations are updated to support these new configuration options:

    • AppDynamics
    • AWSCloudWatch
    • Dynatrace
    • New Relic
    • ServiceNow
    • Splunk
    • Zabbix

  • Support of Amazon Simple Email Service (SES): Amazon Simple Email Service (SES) is now supported with email notification integration. For more information, see Creating email notification integrations.

Resolving incidents and alerts

  • Jira integration for ticketing: You can now integrate with Jira to enable connectivity to Jira tickets. When the Jira integration is up and running, you can create a policy that opens an incident within Jira by selecting the integration from the Open a ticket area of your Promote alerts to an incident policies. For more information, see Steps 12 and 13 of Promote alerts to an incident. For more information about setting up the integration, see Creating Jira integrations.

  • User experience improvements: Several enhancements and updates to the incident management experience are included to improve improve usability, streamline workflows, and provide a more intuitive user experience. These enhancements include the introduction of horizontal alert tabs for probable cause alerts, inline edit capability for incident titles, and minor styling updates:

    • (Incident Overview Right Side Panel) Incident Title with Inline Edit Capability: You can now add and edit incident titles directly within the panel. There are also some minor styling updates to enhance the overall user experience.

    • (Probable Cause alerts) Horizontal Alert Tabs: Alert tabs have been redesigned from vertical to horizontal for easier navigation.

    • (Probable Cause alerts) Associated Automations in Table View: Associated automations are now displayed in the same tile in a table view, making it easier to see which runbooks apply.

    • (Probable Cause alerts) Remove All Associated Automation Section: The section for all associated automations has been removed to streamline the interface.

  • Addition of Event enrichment: You can use event enrichment to enhance alerts or incidents by updating their standard attributes or populating custom attributes such as, adding, updating, or removing them. For more information, see Event enrichment.

Managing applications (services) and viewing topologies

  • Collapsible incidents panel: When viewing topologies, the (collapsable) Incidents panel opens on the right hand side by default. For more information, see Viewing and modifying a topology.

  • Tabular view filtering and sorting: When viewing resources in tabular format, you can use this panel to dynamically sort or filter the resources displayed to show only those resources affected by the selected incidents. For more information, see Tabular view.

  • Resource filters: Resource filters let you use resource properties to either include or exclude all resources with these properties from having a rule applied to them. You can add more than one property as a filter. Resource filters cannot be set for history or event rules. For more information, see the various rules topics.

Automating processes (Policies, Runbooks, Actions)

  • Enable or disable policies toggle: a toggle for enabling or disabling a policy is now available on the Details page for seasonality and temporal policies.

  • Fully automated runbook conditional branching: You can administer conditional branching for fully automated runbooks. This allows you to run another action if the current action does not have a successful exit status. For more information, see Adding actions.

  • Preview runbook parameter view: The side panel on the Preview runbook page now includes the runbook parameters.

  • Runbook improvements: Miscellaneous improvements for the runbook related tables:

    • The runbook library table and the automation actions table have been aligned.
    • You can publish runbooks directly from the runbook library table.
    • Runbook activities that have been invoked automatically and that are still in progress are protected from manual interaction.

Non-production (tech preview)

  • Visualizing analytics with IBM Cognos Analytics:, the supported capabilities when integrating with IBM Cognos Analytics are improved:

    • You can integrate with IBM Db2 to store alert and incident data in the Db2 database. With this integration, you can create policies to send the alert or incident data from IBM Cloud Pak for AIOps to populate a dashboard or report in IBM Cognos® Analytics.

      For more information about creating this integration, see Creating an IBM Db2 integration. For more information about using policies to send data for a dashboard or report, see Populating a dashboard or report.

    • A new Incident list widget and Button widget are available for use in building a custom dashboard. For more information about the available widgets that you can use, see IBM Cloud Pak for AIOps widgets within IBM Cognos Analytics.

    • Example dashboards are now available to help you learn about the capabiltities of the available widgets and to help you create your own dashboard. For more information about creating a dashboard, see Creating a dashboard.

    Overall, this integration provides you with additional tools to create custom dashboards and reports to visualize and analyze your IBM Cloud Pak for AIOps data. When you set up this integration, you can open IBM Cognos Analytics from the Cloud Pak for AIOps console and begin using IBM Cognos Analytics dashboards to build visualizations of your IBM Cloud Pak for AIOps data, such as alert and topology data.

  • Additional feature previews: In addition to the integration with IBM Cognos Analytics, IBM Cloud Pak for AIOps includes the following components and features for non-production use as a technology preview:

    • Incident (Story) prioritization from persistence analysis and golden signals extraction
    • Deploy to single ROSA cluster configured across multiple AWS Zones
    • Multi-zone high availability and disaster recovery (HADR)
    • New data collection functionality for Dynatrace integration

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

Infrastructure Automation

  • Rails upgrade: For Infrastructure Management, Rails is upgraded from 6.1 to 7.0. The library update to 7.0 can remove, change or deprecate features that you might be using in custom Ruby automations, particularly in the usage of the active record and active support gems. Before you deploy Infrastructure Management version 4.7.0 in production, test your custom Ruby automations in a version 4.7.0 test environment. For more information about active record and active support gems in Rails 7.0 see Ruby on Rails 7.0 Release Notes.

  • Install on Google Compute Engine as appliance: You now have the option to install Infrastructure Management as an appliance on Google Compute Engine (GCP). For more information, see Installing on Google Compute Engine.

  • Red Hat OpenShift 4.16: Support is added for Red Hat OpenShift 4.16 for new or upgraded deployments of Infrastructure Automation. For more information, see Learn more.

  • Terraform Runner offline (air-gapped): You can now enable Terraform Runner in an offline (air-gapped) environment. Learn more.

Security and compliance

  • Fixed security vulnerabilities: Fixes and updates are included to address reported security-related vulnerabilities with IBM Cloud Pak for AIOps. For more information about the included fixes, see Security bulletins and fixes.

Documentation changes

In addition to the documentation for the preceding new and changed features, the following documentation is updated:

  • Deployment option documentation:

    • The planning, installing, upgrading, uninstalling and some administering topics for deployments of IBM Cloud Pak for AIOps on Red Hat® OpenShift® Container Platform move under the new Deploying on OpenShift node.

    • The planning, installing, upgrading, uninstalling and some administering topics for deployments of IBM Cloud Pak for AIOps on Linux® move from the technology preview section to the new Deploying on Linux node.

  • Infrastructure Automation documentation: The planning, installing, upgrading, uninstalling and some administering topics for Infrastructure Automation move from various nodes in the documentation to the Infrastructure Automation node.

  • Infrastructure Automation installation topics: The topics for the installation of Infrastructure Automation with IBM Cloud Pak for AIOps have a step added to create the ibm-operator-catalog source. The IBM Cloud Pak for AIOps installation process no longer creates this catalog source because of the changes in New catalogs and revised upgrade process, but Infrastructure Automation still needs it.

  • Health check and monitoring updates: Monitoring with Prometheus and Grafana is now available to monitor your existing installation of IBM Cloud Pak for AIOps. For more information, see Monitoring with Prometheus and Grafana.

Previously introduced features and changes

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