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 category 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

  • Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)

  • Tivoli Application Dependency Discovery Manager - TADDM

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Created by Guest
Created on Nov 6, 2020

Require support for OAuth in Message Bus Probe when connecting to Azure

Support for Azure Secure Webhooks leveraging OAuth2 security with the Netcool Message Bus Probe.

System:
Integration of Message Bus with Azure
Actor: User requires Secure Webhook integration with Message Bus

As our clients adopt more Cloud-native environments and securing the communications with these newer technologies advances, the monitoring and event management solutions developed by IBM need to keep up to date.

Description:

A CSP / MSP customer is monitoring their Cloud environment using Azure, sending out events as Webhooks.

As the client is security conscious they have asked for communications between the Netcool Message Bus Probe and Azure to be secured with OAuth 2.
The probe itself has the capability to support OAuth2, but when deploying this with Azure it was identified that the integration is failing wafter a 120-second timeout.

From research, it was identified that a standard Webhook integration works with Azure secured via a certificate, but the problem and drive for this RFE is to fix the issues when integration with an Azure Secure Webhook and provide support.

Idea Priority High
Use Case
System: Cloud-based monitoring solution Actor: Operations Monitoring Team Use cases for the system: The client has moved to a cloud-based environment for some of their operations and receives monitoring events via Webhooks. As the client is security conscious and requires that any cloud to on-premise monitoring communications needs to be at the OAuth2 as the data going over the Internet is of a sensitive nature. Scenario: 1. Configure Netcool Message Bus with Azure via Secure Webhooks 2. Start-up the Probe 3. The probe connects to Azure and authenticates via OAuth2 providing back a Token 4. The probe then sits on the http (ssl) channel waiting for Webhooks to be delivered 5. The probe processes these alerts into OMNIbus events for subsequent processing in the ObjectServer Current Behaviour: After step 3 in the above scenario - 1. Zero or more events are received from Azure 2. At the 2-minute point (give or take a few seconds) the probe loses connection with Azure and shuts down.
RFE ID 146574
RFE URL
RFE Product Tivoli Netcool/OMNIbus Probes