We often end up building a new alert using the exact same conditions when a team says "Hey, we want our CPU/Memory/Widget X alert delay to be YY minutes instead of ZZ minutes." The only reason we create the new alert is to change the alert trigger and/or reset delay.
I propose that the option for a custom property option be added so that we can specify delay by using node/application/volume/interface (as defined by the alert scope) custom property to define the delay and reduce the number of duplicate alerts.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.
Learn more today by joining now.