Skip to Main Content
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

  • 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 Not under consideration
Created by Guest
Created on Feb 2, 2017

To have a easy way to know which targets in scope were unreachable during the discovery

In our environment we usually run discoveries on big scopes. It could happen that some targets included in the scope were unreachable through ping. We are looking for a simple way to have a list of scoped targets, for each of them having the simple information if during the discovery it was possible to ping it or not.

After involving TADDM support on this request, we were informed that there is not any simple way for that. The information about ping failures is only traced in ping sensor log files, but anyway it is not possible to explore them in a simple way, considering that most discoveries include anchors and the ping logs are present both on TADDM DS and on any single anchor (eventually chained).

Idea priority Urgent
RFE ID 100439
RFE URL
RFE Product Tivoli Application Dependency Discovery Mgmt (TADDM)
  • Guest
    Apr 16, 2019

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Cloud
    Product family - Operations Management
    Product - Tivoli Application Dependency Discovery Mgmt (TADDM)

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Operations
    Product - Tivoli Application Dependency Discovery Mgmt (TADDM)

  • Guest
    Feb 3, 2017

    You could base a report on differences between on differences between BB_COMPUTERSYSTEM40_V and BB_OPERATINGSYSTEM62_V.

    Whenever a Ping discovery is run, BB_COMPUTERSYSTER40_V receives an update when the DNS entry still exists, but as long as the OSSensor is not run, the lastmod date of BB_OPERATINGSYSTEM62_V is not updated.

    We use this to identify login problems, but it could work for your purpose as well, assuming you're using L2 discovery. Good luck!

    ps. I'm not an IBM employee or representative :)

    The query:
    select
    A2.FQDN_C, A2.CONTEXTIP_C , A2.LASTMODIFIEDTIME_T as "SYSTEM MODIFIEDTIME", A1.LASTMODIFIEDTIME_T as "OS MODIFIEDTIME", A1.OSCONFIDENCE_C
    from cmdb.bb_operatingsystem62_v A1
    join cmdb.BB_COMPUTERSYSTEM40_V A2 on a1.PK_C = A2.PK__OSRUNNING_C
    where
    -- Time difference between system update and os update is more than 2 days:
    (A2.LASTMODIFIEDTIME_C - A1.LASTMODIFIEDTIME_C) >= 2*3600*24*1000
    and
    A1.osconfidence_c = 100
    and
    -- where not interested in systems that haven't been seen at all for 21 days.
    A2.LASTMODIFIEDTIME_C >= (((TRUNC(sys_extract_utc(SYSTIMESTAMP),'MI') - to_date('01-JAN-1970','DD-MON-YYYY')) * (86400) * (1000)) - (21*3600*24*1000))