Skip to content
Hyperion

Read your notifications

Hyperion writes an alert to the notification bell whenever a site goes down, a certificate fails to renew, pages break, a WordPress update needs a hand, a site runs out of PHP memory or disk quota, or a server’s filesystem turns read-only. Alerts from worker nodes are collected on the master, so one list covers the cluster. The bell needs no setup. Email and Slack copies are set up in Set up alert channels.

Before you start

Section titled “Before you start”
  • You are an Owner or an Administrator. By default only those two roles receive notifications. Each of them keeps their own read state, so marking an item read affects only you.

Steps

Section titled “Steps”

Use the bell

Section titled “Use the bell”
  1. Look at the bell at the bottom of the sidebar, beside your name. A badge counts your unread notifications.
  2. Click the bell. The dropdown lists the newest ten.
  3. Click an item to open what it is about. Opening a notification marks it read.
  4. Click Mark all as read to clear the badge, or View all notifications for the full list.

Search the archive

Section titled “Search the archive”
  1. Click the bell, then View all notifications. The Notifications page keeps 90 days of history.
  2. Read the line under the title. It summarizes what needs you, with an Open → link when it points at one item.
  3. Narrow the list:
    • Type in the search box, which matches the site, title and message.
    • Choose a topic from Every topic: Uptime, Certificates, Broken pages, WordPress, Site mail, PHP, Disk quota, Server, Trash, Protection or Other. The list shows only topics that have rows.
    • Click All, Unread, Errors, Warnings or Info. The segments carry counts.
  4. Read each row: severity, title, topic tag, a node tag when it was raised on a worker, the message, and the time. Hover the time for the exact timestamp.
  5. Click Mark read on a row, or Mark all read at the top. With a filter active the button reads Mark these read and applies only to the rows that match.
  6. Click Older notifications → at the bottom for the next page, and ← Newest to go back.

The severity colours mean:

Severity Meaning
Error (red) Something is broken now: the site does not serve, a certificate has expired, malware is on disk
Warning (orange) Something will break or a promise is unmet: a certificate expiring next week, a plugin that needs a hand
Info Worth recording

Alerts that restate one ongoing fact, such as a site that keeps hitting its PHP worker limit, replace their earlier card instead of adding one. The Alert channels button on the page opens Settings, Alerts.

Check that it worked

Section titled “Check that it worked”
  • The bell badge matches the Unread count on the page.
  • After Mark all read, click Unread. The list reads “Nothing unread — you are caught up.”
  • A monitored site that goes down appears as an Error under Uptime. See Monitor a site’s availability.

If it fails

Section titled “If it fails”
  • “No notifications yet”: nothing has been raised in 90 days.
  • “No notifications match these filters.”: clear the search and topic, then click Show every notification.
  • An alert from a worker is missing: the master collects a worker’s alerts from the node. Check that the node is online on Nodes and on Service health.
  • You see no bell activity but expect alerts: your role is not Owner or Administrator.
Section titled “Related”