Triggered by uptime alerts
Watchdog can respond when Uptime Monitor signals that a service is down, degraded, or crossing a configured threshold.
Watchdog response
Automated response paths for uptime alerts, bandwidth changes, and Fabric failover.
Watchdog connects monitoring signals, inbound webhooks, cooldown timers, configured bandwidth responses, and temporary Fabric Connections so teams can act quickly without creating noisy bounce behavior.
Uptime alertsInbound webhooksFabric failoverAuto-teardown
Timers prevent bounce behavior
Cooldowns and stable-state timers help prevent repeated up/down flapping from creating noisy or conflicting responses.
Fabric failover actions
Response rules can temporarily stand up a Fabric Connection for another path, then tear it down when the primary service recovers.
Trigger response paths
Let approved monitoring signals trigger bandwidth or temporary Fabric Connection responses.
Custom inbound webhook URLs can receive status changes from outside monitoring systems, log the trigger, run the configured response, and tear down temporary Fabric Connections after recovery.
Uptime Monitor alert or inbound webhook is received.
Watchdog verifies the trigger and current response state.
Configured Internet on Demand or Fabric Connection response is applied.
Cooldown, auto-revert, and teardown timers prevent repeated bounce events.
Ready to automate response?
Book a demo of Watchdog response for Internet on Demand and Fabric Connection workflows.
Share your alert sources, cooldown needs, Fabric templates, and response rules so we can map the right Watchdog flow.