Browser push alerts
Turn on push notifications in a browser, choose who receives them on a site and read the failures the log can show.
Last reviewed
On this page
Browser push sends an alert to the devices of the people you name, as a notification from their browser. It has two parts: each person turns push on for their own browser, and a notification on the site lists the people who should receive it. The rules that decide when an alert is sent are on the alert rules page.
Turn push on in your browser
Push is a personal setting, so every person who wants it does this for themselves. An Admin can't turn it on for someone else.
Open Account
Find the Push Notifications card. It only appears in browsers that support web push.
Choose Enable
The browser asks for permission to show notifications. Allow it. The card then reads Push notifications are enabled.
Repeat on each browser or device
A subscription belongs to one browser profile on one device. Someone who wants alerts on a laptop and a phone enables push on both.
If the browser has blocked notifications for OctoPing, the card says so and shows no button. Allow notifications for the site in the browser's settings, then come back. Choose Disable on the card to stop push on that browser.
Add a push notification
Create the notification
On the site's Notifications page, choose Add Notification and set Notification Type to Web Push.
Enter the recipients
Enter one email address per row. Use the address of each person's OctoPing account. The form's hint reads Workspace members who have push notifications enabled in their account settings.
Choose the triggers and send a test
Choose Send Test. Every recipient with push enabled gets a notification.
A recipient is matched to a person by account email address. An address that doesn't belong to an account, or an account that hasn't enabled push on any browser, receives nothing.
What arrives
- The title is the alert's subject line, the same text an email would carry.
- The body is the first 200 characters of the alert's message.
- Clicking the notification opens OctoPing. For a website alert it opens the site's page. For a heartbeat alert it opens the list of workspaces.
- Notifications about the same site share a tag, so a newer one replaces an older one that is still on screen instead of stacking.
Delivery and failures
| In the log | What it means |
|---|---|
| Sent | At least one device accepted the notification. Delivery to the other devices isn't confirmed. |
| Failed with No active push subscriptions found for recipients | None of the recipient addresses has push enabled on any browser. Ask each person to enable it on the Account page. |
| Failed with Failed to send push notification to any subscription | Every device refused the notification, or couldn't be reached. |
When a browser reports that a subscription is gone, because the person cleared site data or removed the browser, OctoPing marks that subscription inactive and stops sending to it. The person enables push again on that browser to receive alerts there.
Related
- DocsAlert rulesHow a failed check becomes an alert: the retry threshold, the repeat interval, the four triggers, recovery, the default notification, the log and what a maintenance window holds back.
- DocsEmail alertsWho receives an email alert, what the message contains and how to read the notification log when one doesn't arrive.
- DocsAdd your first site, alert and status pageAdd a site, get a first alert through the default email notification and publish a status page, using the app's own labels.
- FeatureWebsite alerts by email, Slack, Discord, webhook and pushChoose where alerts go, how many failures it takes to send one and how often reminders repeat. Recovery messages and a log of every attempt are included.