This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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 - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including 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.