Idea ID 1628928
SMA containers need to output logs to stderr/stdout
DETAILED DESCRIPTION: Please provide a detailed description of your requirements for the enhancement to help us evaluate the feasibility. Include how you think the enhancement/feature should be implemented to best solve the problem.
Provide all log messages to stdout (or stderr) of every container in the suite.
USER IMPACT: Please describe the user impact of this enhancement; the number of users it would benefit, quantitative time savings, etc...
Administrative troubleshooting of the suite is nearly impossible, and inconsistent across suites. Also ability to leverage industry standard tools and/or opsb to aggregate logs for production clusters is basically impossible. It logs are no longer written to nfs, and written to stdout and stderr, suite performance will be improved because that log information/data is not traversing the nfs connection.
BUSINESS CASE: Please include why you believe that this enhancement will be beneficial to a large number of customers/users outside your organization and why it should form a part of the standard product.
Container development standards as expected by the industry expect this functionality . Every customer who needs to troubleshoot one or more suites is stuck digging through countless logs, often many many logs per container. In the case of sma-x, implementing this will at a minimum reduce the number of logs to look through to 90-100. Currently well over 150 logs are written by the suite to the nfs filesyste,.
How frequently would you use this enhancement?
Numerous times per day.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.