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 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)
Adding default component statuses logging to default logging level
In cases TS004816821 and TS004896360 the customer faced problems with setting an optimal debug level to monitor the status of components. In case TS004816821 the customer had a fatal error when LDR did not send any data for approximately 4 days. IBM support did say LDR was analysing and regrouping data, but the customer was unable to get any confirmations of this status from logs. Moreover in case TS004896360 the customer faced a problem with huge backlog data and proviso.log was stopping due to high logging level.
The customer needs a solution, where to default logging level basic statuses of components would be included and would not produce an enormous log due to high debug level data. The created functionality should not be enabled only in the debug mode, but should be included in the regular logging level.
Do not place IBM confidential, company confidential, or personal information into any field.