Skip to content

Testing Your Alerts

Alerting & Contacts 9 min read
On this page

The 7 steps below test your alerting without waiting for a real outage. Each one catches a different way an alert goes nowhere, from an unverified account email to an escalation step with no recipients. If an alert has already fired and nobody received it, Alert Emails or SMS Not Arriving is the article for that.

Before You Start #

  • Integrations live at Alerting → Integrations; only Owner and Admin seats reach them. Contacts, escalations and the previews page are open to Owner, Admin, Editor and Read-only seats alike.
  • Sending a heartbeat test ping needs an Owner, Admin or Editor seat.
  • Escalation policies, alert grouping and acknowledgment require the Professional plan or above. The trial clears that gate.

Step 1: Verify Your Account Email #

While the account email is unverified, Uptimia delivers nothing: no email, no SMS, no Slack message, no webhook. The delivery queue checks verification first. It deletes every queued notification that fails that check, with no retry, no bounce and no error anywhere in the interface.

An amber banner sits across the top of the control panel while the address is unconfirmed, reading Verify your email to receive alerts. followed by "Alert notifications are paused until you confirm" and the account's own address. Click Resend verification email. Open the link it sends. Uptimia allows 3 sends an hour; a fourth attempt answers "Please wait a moment before requesting another email."

Only the account owner sees the banner, because verification lives on the owner account, but the block is account-wide: until it clears, nobody can create an Uptime, SSL, Domain, Speed, Security or Real User monitor.

Step 2: Find Monitors That Would Alert Nobody #

Open the Dashboard. If any monitor has no contacts, no teams and no escalation policy, an amber panel headed No alert recipients — N monitors lists every one, and you cannot dismiss it; the panel clears when each listed monitor has at least one recipient. A silent monitor that is down right now sorts to the top with a Down now, nobody told badge.

Each row's Assign contacts button opens that monitor's editor at its Alerting card. The same state drives a No recipients filter, listed under the More status filter when any monitor has no recipients, and a No recipients badge on the monitor card.

The panel counts the recipients you selected, deliverable or otherwise. A monitor whose only contact is unconfirmed stays off this list; Step 3 catches that one. When a policy is attached, the count comes from the policy's steps rather than the monitor's own list.

Step 3: Read the "Won't Deliver" Badges #

Open a monitor's editor and scroll to the Alerting card. The right pane resolves your selection into the endpoints that would be paged, under the heading Will notify N of M contacts — at once. An opted-out or duplicate row carries a red won't deliver badge, and an unconfirmed row an amber not verified badge. All of them are counted in the header's N won't deliver. Hover a badge to see its reason.

Badge reasonWhat it meansWhat to do
UnconfirmedThe address or number was never confirmed with the link or code in its verification message, so the delivery queue drops its alerts. A new or changed email or SMS contact gets that message automatically.Find it on Alerting → Contacts, where it reads Waiting for verification, Verification expired or Not verified. Click Resend for a new link (and a new code for SMS), or Enter code to type an SMS code. The link works for 7 days, an SMS code for 30 minutes.
Opted outSomeone used the unsubscribe link in an alert email, or chose "This isn't me" in the verification message. The contact stays selected and is never delivered to.Only if the recipient asked for alerts again: on Alerting → Contacts, click Allow alerts next to the Opted out badge, or Allow alerts again in the row's menu. An email address or number gets a new verification message first and receives alerts once the recipient confirms. Deleting the contact and adding it again does not help: the new row starts opted out. See Who Gets Alerted.
DuplicateAnother selected contact already covers this channel and destination. One alert is sent, to that one.Nothing; this one is informational.
The monitor editor's Alerting card: the right pane resolves the ticked contacts into the endpoints that would be paged, with a red "won't deliver" badge against the one the delivery queue would drop.Enlarge

The editor's summary rail repeats the count in one line: "Alerts 2 of 3 contacts after 5 min · 1 won't deliver · recovery alert on". If it says nobody yet, Uptimia refuses to save the monitor until you pick at least one recipient. Who Gets Alerted explains how that resolved list is built.

Step 4: Test Each Integration #

All 10 integration types can send a test: Slack, Discord, Telegram, Microsoft Teams, Mattermost, PagerDuty, Atlassian Statuspage, Twilio, WhatsApp and Webhook.

  1. Go to Alerting → Integrations.
  2. Open the row's actions menu and click Test. A success toast reads "Test notification sent successfully".
  3. Open the destination (the Slack channel, the phone, the receiver's log) and confirm the message arrived.
The Integrations list with one row's actions menu open on Test, Edit and Delete, showing where the per-integration test lives.Enlarge

The toast says Uptimia dispatched the message; it doesn't read the channel's reply. Twilio is the exception: an invalid number fails the test and the toast reads "Test failed: invalid_phone_number". For every other type a dead webhook URL still produces the success toast.

The same Test button sits in the integration editor, grayed out while you have unsaved changes. The test uses the stored credentials, not the ones on screen: "Save your changes before sending a test notification".

The test bypasses the delivery queue, so it goes out even if no contact points at that integration. It does need a verified account email; until then the test fails with "Verify your account e-mail address before sending a test notification." An account can send 5 integration tests every 10 minutes. A passing test proves the credentials work and nothing more.

Email and SMS contacts have their own test. On Alerting → Contacts, a verified contact has a Send test button (Owner, Admin and Editor seats). It sends a sample Down alert marked TEST, about an example website, straight to the contact through the same mail relay or SMS route a real alert uses. A test SMS uses an SMS credit like a real alert. Each contact takes 5 tests an hour and the account 20; Free and trial accounts also get 1 SMS test and 10 email tests a day.

The Alerting → Contacts page: verified contacts with a Send test button, an SMS contact reading Waiting for verification with Resend and Enter code, and an email contact marked Opted out with Allow alerts.Enlarge

Step 5: Preview the Message Each Channel Sends #

Go to Alerting → Escalations and click Alert previews in the page header. The page opens on What the alerts look like.

The Alert previews page showing a sample down-alert email, with the tabs and Message / Channel controls that switch between the 15 renderings.Enlarge

The incident shape comes from 2 tabs: One monitor or Grouped incident. Two segmented controls pick the Message and the Channel:

  • Message, one monitor: Down alert, Recovery.
  • Message, grouped incident: Down digest (the renamed down alert), Recovery, More joined.
  • Channel: Email, SMS, Slack.

The preview shows the subject line, the three-fact strip, the acknowledge block and the SMS wording your runbook has to name.

The page renders sample content rather than your own monitors, and it sends nothing; read it as a reference to what a monitor with an escalation policy attached receives. A monitor with no policy gets the per-monitor message, which carries no acknowledge link.

Step 6: Send a Heartbeat Test Ping #

A heartbeat monitor is the one family you can exercise from your own side.

  1. Open the heartbeat monitor and choose Ping setup from the Actions menu.
  2. Click Send a test ping. The toast reads "Test ping received — marked manual, schedule untouched."
The Ping setup modal on a heartbeat monitor, showing the Success, Start and Fail ping URLs, the copy-paste snippets, and the Send a test ping button.Enlarge

Uptimia records the ping with signal type manual and the user agent you · via dashboard. The ping shows in the ping log and the live feed, but it never arms the monitor and never moves the next expected ping, so a job that has stopped running is still caught. To prove your own cron reaches Uptimia, call the Success URL from the machine that runs the job. See Heartbeat Monitoring.

Step 7: Walk the Escalation Ladder #

Open a policy at Alerting → Escalations. The sticky Preview card replays an example incident ("If a monitor goes down at 09:41"). It opens with "Incident confirmed", then lists each step at its clock time with the people it alerts ("Nobody yet" for an empty step), then the repeat rounds, and closes with "Monitor recovers". Show channels adds each step's channels.

Check the pane for:

  • The amber warning line, such as "1 person won't be alerted · Step 2 alerts nobody". Click it for the list: "Step 2 has nobody to alert.", "Morgan Diaz has no contacts yet." or "<name> hasn't verified a contact yet."
  • A grey dot on a step: nobody on it can be reached.
  • The footer total: "Reaches 3 contacts across 3 people over 45 min".
An escalation policy editor with its Preview pane walking through an example incident step by step. A warning under the preview says step 2 alerts nobody and that a selected person, Morgan Diaz, has no contacts.Enlarge

A read-only timeline of the policy appears in the monitor editor's Alerting card once the mode is Escalate over time. It starts at "Outage confirmed", draws the monitor's alert delay as the first stop when it has one, and marks later steps as "+15 min" and so on. It flags Not verified contacts and people with No contacts only. Opted-out and duplicate rows show in the right pane from Step 3. Escalation Policies covers building the ladder.

Tests With Side Effects #

Warning: Testing an Atlassian Statuspage integration posts a real incident on your public page, titled "Uptimia integration test", with the status Investigating, and if the integration carries a Component ID, the test also sets that component to Under maintenance. Nothing resolves them. Resolve the incident and restore the component in Statuspage by hand afterwards.

SMS verification codes are not charged to your SMS credits, but they are limited: Resend works once every 10 minutes per contact, and Uptimia sends at most 3 verification SMS per contact and 10 per account a day. A Send test to an SMS contact does use a credit. Verify a number once and leave it verified.

The Pre-Launch Checklist #

  • The account email is verified: no amber banner at the top of the control panel.
  • The dashboard shows no No alert recipients panel and no No recipients chip.
  • No monitor's Alerting card carries an unexplained won't deliver badge.
  • Every email and SMS contact on Alerting → Contacts shows Verified, and a Send test reached it.
  • Every integration was tested and the message was seen in the destination.
  • Any Statuspage test incident is resolved and its component restored.
  • Every escalation step in the policy's Preview reaches a real person.
  • Each heartbeat monitor has received a real ping from its own job, beyond the manual test ping.

Was this helpful?

Your answer helps the team improve this article.

Still need help?

Uptimia Bot answers right away and passes you to the team when it can't.

Source: https://help.uptimia.com/help/a/testing-your-alerting-end-to-end