This portal is to open public enhancement requests against IBM System Storage 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
CSM should trigger automatic backup of logs to files
in case of a critical event related to replication occurs. Reason to request this feature >
CSM logs are getting overwritten in a very short period of time that critical events disappear from log and it makes RCA impossible.
Idea priority | High |
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.
So there are actually some events that will trigger automatic log package creation. A failed GM recover command, failed scheduled task or a failed backup are a few examples. The issue with this request is defining exactly what events should warrant an automatic log package. Too "many" log package triggered could affect performance. And each creation of a log package can take up disk space. On and CSM HMC installation, disk space isn't an issue because we will automatically only keep 5 log packages. But on a standalone server, there is nothing that roles older log packages and running out of disk space could cause issues with CSM and other products.
So, I would be greatly interested if you could provide a list of events that you think you'd want to see automatic log packages created for.