What's new in IBM Cloud Pak for AIOps 4.4.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
IBM Cloud Pak for AIOps 4.4.0 delivers new and improved tools for foundation services, automating processes, incident resolution, and more.
The following new features and changes are introduced with this IBM Cloud Pak version:
- Install and upgrade
- Defining integrations
- Automating processes (Policies, Runbooks, Actions)
- Resolving incidents and alerts
- Anomaly detection
- Infrastructure Automation
- Non-production (tech preview)
- Security and compliance
Install and upgrade
-
IBM Cloud Pak for AIOps and Infrastructure Automation both use IBM Cloud Pak® foundational services. In this release, they now consume IBM Cloud Pak foundational services v4 instead of v3. IBM Cloud Pak foundational services v4 does not automatically install a certificate manager or a license service which the previous versions of IBM Cloud Pak foundational services did, and extra steps are required to deploy these in the installation and upgrade procedures. Learn more.
-
The backup and restore of IBM Cloud Pak for AIOps and Infrastructure Automation no longer requires you to build the backup and restore image. The backup and restore image is now available from the IBM Entitled Registry. Learn more.
-
The version of Redis that is used by IBM Cloud Pak for AIOps is changed in 4.4.0. It is recommended that you remove obsolete Redis artifacts as part of your upgrade, such as any obsolete Redis Persistent Volume Claims (PVCs), Custom Resource Definitions (CRDs), and CatalogSource.
-
Deprecated: Support for using the IBM GitOps repository method to install IBM Cloud Pak for AIOps is deprecated and will be removed in a future release.
Defining integrations (connections)
- With Version 4.4.0, the Data and tool connections feature in the IBM Cloud Pak for AIOps console is renamed to Integrations. In addition, connections, such as the available incoming and outgoing connections, are also renamed to integrations.
Automating processes (Policies, Runbooks, Actions)
-
You can provide tags for filtering automations when you are creating automations. You can select from existing tags or create new tags.
-
You can now generate SSH keys with different type and bit size including ECDSA curved keys, manage multiple SSH keys for your script connection, and you can import externally created SSH keys. The new options are provided by means of the API only. For more information, see Automation (runbook) API and search for "PATCH /configuration".
Resolving incidents and alerts
- You can now configure the appearance and behavior of the Incidents list through the Settings .
Anomaly detection
-
Deprecated: The natural language log anomaly detection algorithm is deprecated. As a replacement, use log anomaly detection - golden signals.
-
Deprecated: The statistical baseline log anomaly detection algorithmis deprecated. As a replacement, use log anomaly detection - golden signals.
Infrastructure Automation
-
Infrastructure Automation uses IBM Cloud Pak® foundational services. In this release, it now consumes IBM Cloud Pak foundational services v4 instead of v3. IBM Cloud Pak foundational services v4 does not automatically install a certificate manager or a license service which the previous versions of IBM Cloud Pak foundational services did, and extra steps are required to deploy these in the installation and upgrade procedures. Learn more.
-
Kafka messaging configuration is now required for the appliance setup. It is recommended that you configure the broker on the same appliance where your database is configured. You can only have one Kafka broker per region. For more information, see Upgrading Infrastructure Management appliances.
-
For embedded workflows, Infrastructure Automation provides a mechanism for securely passing credentials to your running workflows. For more information see the section Credentials for Embedded Workflows in the topic Managing Providers.
Non-production (tech preview)
IBM Cloud Pak for AIOps includes the following components and features for non-production use as a technology preview:
- Application disruption costs tile of AIOps Insights (dashboard)
- Log anomaly automated training data selection
- Incident (Story) prioritization from persistence analysis and golden signals extraction
- Feedback learning for statistical baseline log anomaly detection
- Log anomaly model drift detection
- Deploy to single ROSA cluster configured across multiple AWS Zones
- Multi-zone high availability and disaster recovery (HADR)
- Metric Manager Mediation Pack replacement for AppDynamics
- Metric Manager Mediation Pack replacement for Dynatrace
- Metric Manager Mediation Pack replacement for New Relic
- OpenTofu RC
For more information about these feature previews, see Non-production features (Technology preview).
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.
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: