Alerts for Uptime
Setting Up Uptime Alerts and Notifications
You will need to set up Uptime Alerts to notify you or your team in case of website downtime. Let’s get started!
1. Setting up a Delivery Group
A delivery group is a critical component of Uptime Alerts as it determines where and how the alerts will be sent. Follow these steps to set up a delivery group:
- Navigate to settings > delivery groups.
- Name your delivery group appropriately. Consider using names like “Team A” or “Critical Alerts” to help you identify the purpose of this group.
- You can also specify the notification channels for this group (e.g. email, SMS or Integrations).
- Choose the sensitivity. This is how long a site should be down before sending an alert. Choose a sensitivity level that aligns with the criticality of the service you are monitoring. Critical services may require higher sensitivity levels to ensure timely alerts.
You can create a delivery group and set the sensitivity of when to alert them in case of downtime.
You can create multiple delivery groups to route alerts to different teams or individuals based on their responsibilities or the severity of the downtime.
2. Configuring a website rule for Uptime Alerts
Now you have the delivery groups set up, you can add a website rule:
Start by going to the settings for your uptime monitor by clicking Options & Edit.
You can add the delivery groups you want to alert for that website.
This site has two delivery groups selected – one for 1 minute of downtime, and one after 5 minutes.
You can configure multiple website rules for the same website or service. This is useful for sending further notifications if downtime persists. For instance:
- Set one rule to trigger after 1 minute of downtime, sending an alert to the first group.
- Set another rule to trigger after 5 minutes of downtime, sending a separate alert to another delivery group.
- You could set another rule after 30 minutes of downtime which sends a notification to a more senior member of the team.
This layered approach allows for a more granular response to downtime events.
Further Reading