Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories Orchestration
Created by Guest
Created on Oct 17, 2022

Probe for Message Bus - Add EMS failover option

The message bus probe does not support an EMS failover option presently.

The probe should allow the possibility to configure a second EMS endpoint by introducing SecondaryHost and SecondaryPort properties.

In our setup, the customer's EMS cluster consists of two instances where alarms between both instances are fully synchronised, and both instances are able to provide alarm data.

The probe should start processing alarms from the secondary EMS instance when it detects a problem connecting to the primary instance. Ideally, it should also support EMS fail-back by periodically checking whether connectivity to the primary EMS instance is possible.

Currently, the probe only periodically restarts when it loses connection to the configured EMS and tries to reconnect to the same EMS instance after the restart. This is repeated until the probe succeeds in connecting.

Multiple EMS instances are not uncommon, and anyone can benefit from this feature.

Idea priority Medium
  • Admin
    Nov 1, 2022

    Yes, this doesn't apply to CP4NA and does look like it was intended for CP4WAIOps - it should be submitted to that product instead. Marking as not under consideration for CP4NA.

  • Guest
    Oct 19, 2022

    L3's comment:

    Looks like the idea was raised from incorrect Workspace:

    Workspace Cloud Pak for Network Automation

    The probes should fall under category:

    Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio

    Since the Message Bus probe supports several generic & specific transport methods, it would be helpful if the request include specific details on which EMS/transport the customer would like to have this feature.