Modify Alert trigger Interval on the Instance level
It would be great to have the granularity to be able to change the Alert Trigger Interval on an instance in the same way a threshold can be modified on an instance.
Example: Disk Usage on a netapp
There are 100 volumes but one of them needs to be over the threshold for a longer amount of time to cause concern. So the archive log volume will fill up no matter what space is allocated but it is not a concern as long as it is back below the threshold within 1 hour. A custom datasource will not work for this because we would like to alert immediately on all other volumes on this device when they go above the threshold.
daniel_Briseno
Posted 10 years ago·Last reply 2 years ago
17 comments
LM User
·2 years agoBeen waiting about 4 years for this one.
Sarah Luna
·2 years agoI’m happy to announce that this is in development!
Joe Williams
·3 years agoHaving a discussion with a client currently about this exact request. This would be nice to have and as Stuart said, less complex overhead on keeping stuff up to date.
LM User
·3 years ago11 of our audited LogicModules could be returned to the default settings (i.e. made much easier to keep up to date) if this feature were available.
Mitch Grande
·3 years agoBumping this! I’m going to submit it as a feature request in the product as well.
marting
·4 years agoIn addition to the trigger interval, it would be good to have an option to modify alert thresholds on the instance level as well since not all instances are created equal.Nevermind, found it.
LM User
·4 years agoThrowing in my support as a customer for this capability.
Pavandeep Saini
·4 years agoBumping, would be a great feature. much require in the tool.
raul_rtr
·4 years agoIT would be very much appreciated, we already requested to our CSM too.
Adam_sims
·4 years agoBumping. Would love the functionality to tune trigger intervals at any level, similar to thresholds.
Vitor_Santos
·5 years agoThis would DEFINITELY be appreciated (it's something we've also raised to our CSM too). It would ease the management & implementation of custom requests across our different clients for certain 'data sources' without having to create dedicated DS when those requests come).
LM User
·5 years agoThere is an official feature request already in the system for this. It's currently gathering support as in, the product management team needs to know that many customers want this feature before they can prioritize it. Everybody pile on.
Joe_Tran
·7 years agoAs a longtime SolarWinds user, they have NOT always had this capability innately. But they have always had a workaround similar to what is available to LogicMonitor--proliferate the number of logical objects you would have to maintain that controls alert trigger delays. In SolarWinds, this would be Alert Definitions. Not ideal. Hypothetically you could have used a component-level configuration field (notes or description) and used that in a complex SQL/SWQL-based alert definition to achieve this. Also not ideal.
In SolarWinds SAM, they have added (in the past couple of years) the ability to define custom alert trigger delays on a per component basis, natively.
Clayman
·7 years agoBump. I cannot believe this isn't available yet. Most of my experience is with SolarWinds in the past & it has always had this capability.
In my scenario, I've got some remote sites that frequently lose internet connectivity for several minutes. I do not want to trigger an alert each time this happens. I would like to be able to extend the Alert Interval for those specific sites so that they have to be down for e.g. 15 minutes or more before alerting.
Joe_Tran
·8 years ago5 month bump...
Adding this capability to the Alert Thresholding Wizard is another way to go about doing this, which I'm fine with as well. Same concept--allow this at all levels from device groups to datasource instance.
One app I support doesn't give a rat's donkey if CPU is pegged at 100% for more than 30 minutes in the overnight hours, but another app owner want's to know if it's over 50% for 10 minutes. I don't know how to manage without angering one of these teams or juggling overlapping datasources.
Joe_Tran
·8 years agoAlmost 2 year bump....
Using a mechanism similar to what was created for Polling Interval would work beautifully here since we can now assign properties to instances now. I'm imaging that this property would look something like: <DatasourceName>.<DatapointName>.alerttriggerinterval
If it's assigned at the device-level, it applies to all instances. If applied at an instance-level, then it would only apply for that instance.
My team supports many dev teams. One wants to know almost right away if an AWS ELB has incremented an UnHealthHost. And naturally another dev team doesn't care unless it's something that lasts for over an hour.
I really don't want to (continually) manage multiple clones of a datasource LogicModule with the same set of metrics.