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 Not under consideration
Workspace Instana
Categories Self Hosted
Created by Guest
Created on Mar 24, 2022

Extend Instana Server upgrade support version range to support more version jumps

Issue: For Instana server upgrade, there is a limitation that the target version can not be bigger 3 than the current version. For example, Instana 209 can be updated to 211 and 213, but can not be updated to 215.

Workaround: To upgrade from 209 to 221 you have to upgrade in steps. From 209 to 213, from 213 to 217, from 217 to 221.

Business impact: There is almost no way but reinstall Instana server under current upgrade policy.

For Instana deployed on customer site, customer will not upgrade the Instana server frequently. After one or two years, if customer want to upgrade the Instana server, then there is no way to upgrade the Instana server to latest directly. And since there are too many version released, it is not even possible to upgrade the Instana server for each release version.

Request: Extend the supported version for Instana server upgrade so that Instana can upgrade to a server released in more time period (for example, one or two years)

Idea priority Low
  • Admin
    Hubert Hesse
    Mar 31, 2022

    Also note our Version Support Policy as per

    For self-hosted releases, Instana supports the current release and the previous two monthly releases. Agent sensor releases have six months support from release date.

    Updating the version in-use may be required to troubleshoot and resolve reported problems. If you are using an unsupported version, we highly recommend that you update to the latest release.

    bold is highlighted by me,

  • Admin
    Hubert Hesse
    Mar 28, 2022

    Hi He Wu,

    I amended your original request and included the workaround of stepwise upgrades. At the moment, we are not considering this request as we can not guarantee flawless upgrades over more version jumps.

    Can you share more context around your statement: "For Instana deployed on customer site, customer will not upgrade the Instana server frequently. "

    - Can you describe specific examples where that happened or can give customer names directly to me via, so I can understand their context better
    - Any problems in doing upgrades in steps, e.g. 209 to 213, 213 to 217 and so?
    - What keeps the customers from doing regular updates, e.g. once a month? Is it too hard, technically or organizational, i.e. maintenance windows are too hard to organize