This is an IBM Automation portal for Integration 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
In webMethods.io Integration DAF services (edge services) as well as package services, the pub.flow:debugLog service allows for setting a log level (Fatal, Error, Warn, Info, Debug, Trace). Currently, there is no way to configure which log entries will actually be created. Both on the Cloud Runtime and self-hosted runtimes, the server.log will only include messages from pub.flow:debugLog service invocations with log levels Fatal, Error, Warn and Info. It will not include any debug or trace messages.
It should be possible to quickly, easily and temporarily configure the Cloud Runtime and/or self-hosted runtimes to include debug and/or trace messages as well for debugging and tracing integrations.
The workarounds suggested in SI-576665 are not helpful. In practice, the integration ops team will not have access to the edge server’s admin UI for setting the server log level (that is the whole point of running a remote edge server, right?), and they will not want to contact IBM cloud ops team every time they need to debug or trace an integration on the Cloud Runtime.
Being able to debug or trace is a mandatory requirement for enterprise applications. Please consider implementing this in webMethods.io Integration also.
Best regards,
Thomas
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.