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).
Shape the future of IBM!
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
I set up an event to detect JVM Offline incidents and set it as a critical condition, when this is detected an alert is raised and sent to our Teams channel for my team to react to. Following a critical alert we get a grace period alert which is not needed and causes spam messages to our teams. I found a way around this by continuing to use the custom JVM Offline event, but in alert I set it to on event type "Critical" and DFQ a criteria to pick up on the "JVM Offline event" without the grace period.
This worked for weeks, we where getting the offline alerts, with no grace period.
As of the latest build 21/02 Build 243, we are now getting Grace Period alerts again. we monitor a huge network of applications and so when an agent disconnects to update or the JVM actually goes down this can send many alerts for each one effected.
Can we please have under grace period an additional option of "None, ignore, disable" something to set it as not needed for a specific event.
Do not place IBM confidential, company confidential, or personal information into any field.