Monitor Dependencies: Smarter Alert Suppression

Alert fatigue is a real problem. When a core router or upstream link fails, every downstream host appears to go down simultaneously — and your team gets flooded with notifications for an incident that has a single root cause.

MyMonitor365 now supports monitor dependencies. You can designate any ping monitor as a parent for another monitor. When the parent is DOWN, child monitors continue checking and logging incidents, but all notifications — email, SMS, and integrations — are suppressed. Only the parent's alert fires.

This means a single notification tells your team "the upstream switch is down" rather than twenty notifications saying each server behind it is unreachable. When the parent recovers, child monitors immediately resume normal alerting behaviour.

Dependencies are configured per-monitor in the edit screen. You can assign any other ping monitor in your team as the parent. The relationship is visible on the monitor detail page so the dependency is never a hidden surprise when reviewing an incident.

Incidents are still recorded for suppressed child monitors. The full incident log shows the downtime and marks it as suppressed, so you have an accurate historical record even if no notification was sent at the time.

This feature is available on all plan tiers for ping monitors. We plan to extend dependency support to port and blacklist monitors in a future release.