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.
Thank you for your consideration.
1) Agree, but since CSM has the option to choose which alerts are sent to which distributions the user can always choose do they want to see this or not.
3) When session goes out of RPO beyond the Warning threshold CSM does not mark the session into a Preparing status, so when RPO returns it will not make the session Prepared again, and thus no opportunity for an event is generated. So possibly this is an opportunity for CSM to look at not considering a session which may be as like an hour out of sync as being "Prepared".
We can look at this but the concerns with providing normal events were the following:
1) There are already a lot of events and adding normal events could add to the flood of events users have to manage.
2) The primary reason for alerts is to tell customers that they need to take action or look into something. If there is a case like an RPO alert that might go up and down multiple times, this could lead a customer to thinking things are good when really they should be looking into the cause of the initial warning/severe alert. So it's better that they take a error alert and go into the GUI to find things are now good, then to assume things are good based off a normal event.
3) The majority of alerts are also tied to session state changes. For example, a catastrophic error would cause a session to go into the Suspended state. When the session is restarted it should eventually go back into the Prepared state, which this RFE would result in a Prepared alert as well as a Normal alert.
But I do understand your request based off the RPO type event, so we can look into this feature.