This is an IBM Automation portal for Cloud Management and AIOps 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.
Bridgitte,
SevOne Alert Policies already support email delivery to multiple addressees including:
One or more email addresses
SevOne users (provided email address are configured in their profile)
User roles (emails to all users belonging to a role e.g., "Administrators", provided they have email addresses configured)
Aside from the explicit lack of a CC field, I imagine this could accommodate your use case. Additionally, alert policies can be customized with trigger/clear condition messages that include both the dynamic information that's included in the default messages (device/object/indicator names, data values, etc.) and any custom information you'd like to pass along.
Additionally, many of our customers have adopted webhooks to send alerts to their ticketing systems and then rely on those external systems to parse & route certain alerts to certain users. In those cases, custom fields and values are embedded in the webhook message. Depending on the values of those key-value pairs, tickets could be suppressed, aggregated, or delivered to specific teams responsible for the alerts.
If there are reasons why you don't think either of these methods would work for you, please let us know.
Regards,
Ryan Wilson, Product Manager, SevOne NPM
ryan.wilson4@ibm.com