Feature Request: Per-Device Alert Delay (Only Alert if Offline for X Minutes)

Hi Atera Team,

I'd like to request a feature that would significantly improve monitoring for environments with devices that experience brief or intermittent connectivity issues.

Use Case :

Many of my customers have surveillance systems that consist of:

A Camera Server (Windows PC)
Multiple Generic Devices representing IP cameras on the customer's network

Some cameras may briefly disconnect dozens or even hundreds of times per day due to aging network cabling, camera hardware issues, or temporary network instability.

Current Problem :

Atera generates an alert every time one of these devices goes offline.

This results in:

Hundreds of unnecessary email alerts each day to me and my customers
Alert fatigue
Important alerts (such as the Camera Server going offline or a RAID failure) getting buried in the noise

Proposed Feature Request:

Add a configurable option for any monitored device (PCs and Generic Devices or Scripts because I have a script that detects when my USB attached Raid Arrays go off which is where all camera footage is stored honestly this is absolutely the most important alert they get if that is offline they are no longer recording):

Only alert if device has been offline for X minutes

Example configuration:

Camera Server , Raid Array
Alert immediately (0 minutes , Default Setting for Atera)

Generic Devices
Alert only if offline for 30 minutes or whatever we set it at.

If the device reconnects before the configured delay expires, no alert should be generated.

Why This Matters:

For many of my customers, this isn't just a convenience.

They are required by state regulations to document camera outages that exceed 30 minutes. If a camera remains offline longer than that threshold, they must complete and submit an outage report to the regulating agency.

Because of this requirement, simply disabling alerts on problematic cameras is not an option. We still need notifications but only when the outage becomes significant. (like over 30 mins exactly in my case)

Expected Behavior for this feature :

• Device goes offline.
• Atera starts an offline timer. (which I set that timer period)
• If the device comes back online before the configured threshold, no alert is sent.
• If the device remains offline longer than the configured threshold, send the normal offline alert.
• Once the device recovers, send the normal recovery notification.

Benefits

This feature would provide several advantages:

• Significantly reduce alert fatigue for MSPs and customers.
• Ensure important alerts aren't buried beneath hundreds of transient device notifications.
• Help our organizations remain compliant with regulations that require reporting prolonged outages.
• Reduce unnecessary email volume, which could lower the number of outbound notifications Atera has to generate and process. At scale, that could reduce load on your notification infrastructure while also improving the customer experience.

This would dramatically improve the signal-to-noise ratio of monitoring without changing existing alert behavior for customers who don't enable the feature.

Thank you for considering this request. I believe this would be valuable for surveillance deployments, IoT environments, and any customer who monitors devices that may experience brief connectivity interruptions while still requiring reliable alerting for prolonged outages.