Modify Alert trigger Interval on the Instance level

I’m happy to announce that this is in development!

Bumping this! I’m going to submit it as a feature request in the product as well.

11 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.

In 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.

Been waiting about 4 years for this one.

Almost 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.

Bump. 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.

This functionality would be nice to have. We currently have many teams in our portal, and I've routinely had to clone DataSources to solve this issue. You can already alter the threshold at the group and instance level but it would be nice to modify the trigger interval for that threshold. For instance, we have several teams that want to be made aware immediately when the status of their interfaces goes down, but other teams would rather it be down for several polling cycles before being alerted. Having multiple DataSources solves this but turns into a decent amount of upkeep. 

On 7/27/2021 at 11:11 AM, Stuart Weenig said:

There 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.

This 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).

Having 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.