Skip to content

Send alerts to email, Slack and webhooks ​

EdgeComet sends alerts to email addresses, Slack channels and webhooks that you set up under Alerts > Notifications. Each destination takes the alerts at or above its own minimum severity. The dashboard calls each destination a channel.

A destination can be switched off without being removed, and each one can be sent a test. A website holds up to 20 destinations.

A master switch mutes the whole website without losing the setup, for example during a migration.

The Alert Notifications page on edgecomet.com. The Notifications card holds the master switch for the website, on. The Email channels card lists two addresses, max@edgecomet.com and a second address blurred, each with a switch, a Warning minimum severity, Send test and a delete button, above the Add email address field with the placeholder name@example.com, a Warning selector and Add

Before you start ​

EdgeComet adds the website owner's account address as the first destination, at the Warning minimum, when the site is created. If you later change the account email, that destination follows it.

Only the destinations listed on this page receive alerts. Team access to the website does not add anyone.

Add an email address ​

  1. Open Alerts > Notifications.
  2. Under Add email address, type the address.
  3. Pick the minimum severity: Warning sends warning and critical alerts, Critical sends critical only.
  4. Press Add.

Each address then has its own row: a switch to turn it off and on, the minimum severity, Send test, and a delete button that asks "Alert notifications for {domain} will no longer be sent to {address}. Continue?". An address cannot be edited: remove it and add the new one.

Send alerts to Slack and webhooks ​

Slack channels and webhooks receive the same alerts as email addresses: each has a minimum severity, a switch and a test send, and counts toward the website's 20 destinations.

A Slack channel puts alerts where your team already talks, instead of one person's inbox. A webhook hands each alert to the tools you already run: an incident tool, a ticket queue or your own automation.

Who gets which alert ​

Every destination receives the website's alerts at or above its minimum severity. Info alerts are never sent; they appear in the product only. See Severity.

  • One email per check: alerts that fire in the same check go out together, the most severe first.
  • Recovery: when an incident clears on its own, the destinations that got it receive a recovery notice, with how long it was open.
  • Escalation: when the AI reading raises an alert to critical, destinations set to Critical that did not get it before receive it then.
  • Snooze and repeats: a snoozed incident is sent when the snooze ends, if it fired less than 24 hours earlier, and an incident that carries on after its cooldown is not sent again. See Repeat fires and the cooldown.
  • Failures: if one destination fails, the others still receive the alert. EdgeComet retries a failed send for up to 15 minutes, and an alert that could not be queued is picked up again on later checks while it is less than 24 hours old.

The incident page shows what happened under How this was detected > Notified, such as "Emailed {time}" or "Not emailed: below every channel's minimum severity".

Send a test ​

Send test sends a sample alert named "Test alert" to one destination immediately. It works even when that destination is switched off or the website is muted, which helps you debug a quiet setup. The row then shows "Test email sent", or "Failed to send the test email."

Mute a website ​

The Notifications switch at the top is the master switch: "Master switch for this website. When off, no channel sends anything; channels and their settings are kept."

Rules keep checking and incidents keep opening while the site is muted. Alerts that fired while muted are not sent later when you unmute.

Muting also stops the email that announces a site analysis, but not the weekly performance email. See Weekly search and AI performance email.

What an alert email contains ​

Alert emails come from EdgeComet Alerts. The subject starts with [Alert], the severity and the site, then what happened:

text
[Alert] Critical on example.com: 9 pages failed to load in 36 seconds
[Alert] Critical on example.com: 11 pages changed Hreflang
[Alert] Critical on example.com: Noindex on live pages + 1 more
[Alert] Resolved: Origin stopped answering on example.com
[Alert] 2 issues resolved on example.com

The email waits up to a minute for the AI reading of the incident, which usually lands within seconds. Each alert in it carries:

  • The rule and the headline: the severity, the rule's name linking to the incident, and what happened, such as "Clicks fell 30.5%, from 226 to 157".
  • Context: when it happened, who got the error, such as "All 9 were pre-cache renders; no bot or visitor request failed.", where it hit, such as "By section: 7 in /author/, 4 in /category/ and 3 elsewhere.", and the stake: "These 136 pages earned 8,420 impressions in the 28 days before this fired."
  • Pages: up to five affected pages with their impressions. For Pages changed, each page shows what moved, as "was" and "now" pairs or short phrases such as "200 → 404".
  • The AI reading: the verdict and the likely cause, such as "Likely cause · AI reading".
  • A button: Open incident for one alert, Open alerts for several, and a line with the window the rule read and its threshold.

An email with several alerts lists them all at the top and shows full details for the first three. A recovery email reads "Cleared at 14:05 UTC, 3 hours after it fired" and "A later check no longer met the rule, so it closed on its own." The steps to fix an alert stay on the incident page.

Stop alert emails to an address ​

The footer of every alert email reads "You receive these emails because alerts for {domain} are sent to {address}." with Stop sending to this address. The link opens a page titled Stop alert emails?, and Stop these emails confirms. The extra click keeps mail scanners from switching an address off by following the link.

The address is switched off, not deleted, and you can switch it back on under Alerts > Notifications. The site analysis emails to that address stop too.

If it does not work ​

No alert email arrived ​

Open the incident and read How this was detected > Notified:

  • "Not emailed: info alerts never email": the rule is info. Raise its severity with Edit. See Edit a rule.
  • "Not emailed: notifications are off for this site": the master switch is off. See Mute a website.
  • "Not emailed: no email channel is set up": add an address. See Add an email address.
  • "Not emailed: below every channel's minimum severity": a warning alert met only Critical destinations. Lower one to Warning.

If the incident says "Emailed", check your spam folder for mail from EdgeComet Alerts, and check that the address is still switched on.

"This website already has the maximum of 20 channels." ​

Remove a destination you no longer read. Switched-off destinations count too.

"A channel with this address already exists." ​

The address is already on the list, perhaps switched off. Switch it on instead.

Where to find it ​

In the dashboard: Alerts > Notifications.

Next ​