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,
Post an idea
Upvote ideas that matter most to you
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 a notification 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.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
Disable (unused) auto-scaling in ITM shared-service by default
Deliver the ITM system monitoring shared-service default with auto-scaling disabled.
Current default ptypes of ITM have the auto-scaling feature enabled. This can lead to the auto cloning of the RTEMS VM by the system. The extra RTEMS VM however is not used in the communication from the ITM agents. We have also seen that the auto cloning of the RTEMS VM can lead to error situations where there is a extra 'ghost' RTEMS VM and the ITM instance is in Error status. See PMR 70963,211,788.
From a customer perspective when deploying the ITM System Monitoring Shared Service instance a customer has to make a decision on the amount of ITM-agents that the ITM environment must handle (small, medium, large).
After that the topology of the ITM environment in terms of ITM VMs (ITM Datawarehouse, ITM-HUBTEMS, ITM-RTEMS) is static.
From tests performed in the IBM lab. see 12 steps below (as part of PMR 70963,211,788) the auto-scaling can be disabled/paused. It would be very useful to have this as the default, as the auto-scaling is not used by ITM agents and could cause issues.
1. Customized the ptype-itm to scale-out when active agent count is over 40 and scale-in when active agent count is less than 30.
2. Deployed ITM SS with the customized ptype-itm
3. Autoscaling is enabled (active) by default.
4. As the no. of active agents (OS and Q9) running (on existing deployments) were over 40, scale-out operation was triggered on Remote-TEMS thereby provisioning a new RTEMS node.
5. Manually stopped Q9 agents on all the nodes and also manually stopped few deployments to bring the active agent count to less than 30.
6. Within few minutes scale-in operation was triggered on Remote-TEMS and the provisioned new RTEMS nodes was deleted.
7. Disabled (Paused) the autoscaling feature (Manage -> Operations -> Autoscaling -> Pause -> Submit)
8. Manually started all the Q9 agents and started all the stopped deployments.
9. The active agent count went past 40
10. Scale-out operation was not tirggered, even after waiting for 10+ hours.
11. Enabled (Resumed) the autoscaling feature (Manage -> Operations -> Autoscaling -> Resume -> Submit)
12. Within few minutes scale-out operation was triggered on Remote-TEMS and a new node was provisioned.
Do not place IBM confidential, company confidential, or personal information into any field.