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 Under review
Created by Guest
Created on Mar 18, 2024

Allow more than one servicenow observer job to run which will allow us to improve observation times and more control over when/what we collect

At the moment whilst you can create more than one servicenow observer job, it is pretty useless as even though they have different job names and a different set of classes associated in discovery what tends to happen is that you might have a job to discover services, application and server information and this runs fine, creates the topology data you want.


But then lets say you've split it discover network devices, routers, switches etc in a separate job, it starts of discovering these and they get added and then when it discovers the relationships it then proceeds to delete all of the data from the first servicenow job.


Having the ability to control discovery so we could discover large sets of data unlikely to change much which we might kick off once a week and then data likely to change like servers, load balancers, network devices etc which could run more frequently would allow us to improve on the observation time and allow more frequent discovery from servicenow.  


ie data discovered by one servicenow observer shoudln't get deleted if a second servicenow observation from the same servicenow instance is executed.

Idea priority Medium