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 for resolution.

For more information about IBM's Ideas program visit

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

try/catch in Impact Policy should give full stack trace

When writing Java Script Impact Policies I noticed the following:
In the below code example Log(error.stack) seems to only output a truncated stack
trace, which isn't really much use in debugging. I see that I can use error.message,
but that does not give me the same output as if I hadn't bothered with try/catch at
all. It would be nice if error.stack offered full output (see below for

try {
//some code
catch(error) {
Log("An error occured during policy Execution...see stack trace below.");
finally {

//some code


When ran against an example I got the following output:

20 Nov 2020

12:08:41,467: [TEST_TT_MonitorAutoticketJS][pool-2-thread-102283]Parser

log: An error occured during policy Execution...see stack trace below.

Log(error.stack) output: 20 Nov 2020

12:08:41,468: [TEST_TT_MonitorAutoticketJS][pool-2-thread-102283]Parser

log: at pool-2-thread-102283:733 (main)

at pool-2-thread-102283:1069

Log(error.message) output: 20 Nov 2020

12:08:41,468: [TEST_TT_MonitorAutoticketJS][pool-2-thread-102283]Parser

log: com.micromuse.common.util.NetcoolException: Die Datenquelle

NCOMS_SPUx ist nicht vorhanden.

For error.stack I would have expected something like:

20 Nov 2020

12:03:03,691: [TEST_TT_MonitorAutoticketJS][pool-2-thread-102233]Caused

by: org.mozilla.javascript.EcmaError: TypeError: Cannot find function

printStackTrace in object JavaException:

com.micromuse.common.util.NetcoolException: Die Datenquelle NCOMS_SPUx

ist nicht vorhanden.. (pool-2-thread-102233#‌1082)
























Idea priority Medium
RFE ID 147027
RFE Product Tivoli Netcool/Impact