Cloud Management and AIOps

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Please use the following workspace to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):

  • Cloud Pak for Multicloud Management

  • Cloud Pak for Network Automation - incl Orchestration and Performance Management

  • Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio

  • Control Desk

  • Edge Application Manager

  • IBM Observability with Instana

  • ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8

  • Workload Automation - incl Workload Scheduler

ADD A NEW IDEA

FILTER BY CATEGORY

All ideas

Showing 171 of 171

Correlation-id based logging approach when provisioning infrastructure

New correlation-id should be created for each API call/request and should be carried forward to the subsequent internal calls to the other microservices. All logs should be prefixed with the correlation-id (supported by many logging libraries) I...
Guest about 2 years ago in Cloud Pak for Multicloud Management Ideas 0 Under review

Allow MCM Console UI customization through widgets

While IBM is trying to bring together most of the features in a single pane of glass (individual product consoles slowly getting unfied), there will always be some features specific to customer which should be pluggable by customer. MCM console s...
Guest about 1 year ago in Cloud Pak for Multicloud Management Ideas 0 Future consideration

NOI v1.5 event count tools

In the event count patch (netcool-omnibus81017-eventcounter.tar.gz) of OMNIbus the tool is limited to non fail over architectures. I need this tool to support fail over architectures as soon as possible as a deal at a banking customer is pending o...
Fred Harald Klein over 2 years ago in Cloud Pak for Watson AIOps 1 Future consideration

Application and Event monitoring statefulset operators

The community around the operator pattern and the community framework has gained a lot of traction and has matured quite a bit from its original proposal and delivery. There are increasingly more examples of technologies adopting this pattern (htt...
Guest over 1 year ago in Cloud Pak for Multicloud Management Ideas 0 Future consideration

Operator pattern based deployment lifecycle management for the Application and Event monitoring workload

Refactor the ibm-cloud-appmgmt-prod helm chart to be replaced by a go-sdk operator for controlling the deployment lifecycle, administrative and operation tasks of the IBM Cloud App Management workload. Note: Not to be confused with using a helm-t...
Guest over 1 year ago in Cloud Pak for Multicloud Management Ideas 1 Future consideration

Vertical scaling of Application and Event monitoring stateful services

A means by which to effectively perform vertical scaling of key stateful services in the `ibm-cloud-appmgmt-prod` chart. Today, the stateful services include PersistentVolumeClaims in their pod spec, and use helm values to configure the size of t...
Guest over 1 year ago in Cloud Pak for Multicloud Management Ideas 0 Future consideration

Enhanced Placement Rules

Allow for additional inputs into the placement rules. For example: cost of resources within a cluster, network latency of a cluster (ex: edge vs central cloud), networking capacity between locations, cluster hardware capabilities (CPU pinning, GP...
Guest over 1 year ago in Cloud Pak for Multicloud Management Ideas 0 Under review

Enhanced Visibility of Deployed Application Versions.

Update the topology, application, and/or overview screens in MCM to more effectively see what release(s) of applications are deployed to which clusters. These views should be consumable even when there are 100s of clusters and support grouping by...
Guest over 1 year ago in Cloud Pak for Multicloud Management Ideas 0 Future consideration

More control for application updates at scale

When doing an application update (such as from v1.0 to v1.1) for multiple Deployables each deployed in their own cluster, the customer needs more control over how those upgrades are performed. The ability to do a canary deployment (upgrade just on...
Guest over 1 year ago in Cloud Pak for Multicloud Management Ideas 0 Future consideration

Rolling upgrades for a single Deployable

When doing an application update (such as from v1.0 to v1.1) for a single Deployable, MCM should support Kubernetes rolling upgrades for each service in the application so that the application can be upgraded with zero downtime. Our understanding ...
Guest over 1 year ago in Cloud Pak for Multicloud Management Ideas 2 Future consideration