IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for Watson Supply Chain solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain
Connect with IBM experts and your peers on the
Supply Chain Collaboration Community and the Order Management Interest Group
Submit ideas for other Watson Customer Engagement Products:
• Watson Marketing
• Watson Campaign Automation
• Watson Commerce
I've found myself in a Catch-22 scenario when reporting B2Bi issues to IBM. IBM requests debug level logging from the time of the error, but IBM also tells us we shouldn't leave logs set to debug. So we usually have to try to recreate the issue while our logs are set to debug. I've recently had a scenario where a client receives the same error daily. To try to capture details, I have to wait until just prior to the error to turn debugging on, then turn debugging off after the error on multiple logs.
It would be nice if you could setup a timer functionality to say "between 4:00 - 4:15 pm today, set the following logs to debug" and after the timeframe ends, it automatically resets the logging to the previous value.
Even if this functionality could not be made available, if we could get the ability to set multiple logs to debug simultaneously, instead of having to manually enter each log, that would be beneficial as well.
How will this idea be used?
It will be used to near-instantly update multiple logs to assist in troubleshooting and capturing of errors.
|What is your industry?||Financial Markets|
|What is the idea priority?||Low|
|Link to original RFE|