Alerts & notifications

Route monitor events through channels PingBeacons supports.

Use workspace email alert contacts, the in-app inbox, and event preferences to control how failures, recovery, and certificate events reach responsible people.

Start monitoring Read the documentation

Incident event

routes to

In-app notification

Email alert contacts

Email contacts

Attach active workspace addresses to monitors.

In-app inbox

Track unread and individually read notifications.

Event preferences

Control down, recovered, and SSL expiry delivery.

Workspace scope

Keep contacts and preferences inside context.

01Event routing

Send supported events to the right destinations.

Monitor failures, recovery, and SSL expiry can route to email alert contacts and the authenticated in-app notification inbox.

Notification routingPingBeacons

Monitor eventPublic API is down

Email contactsOperations · active

In-app inboxUnread notification

DownRecoveredSSL expiry

02Alert contacts

Maintain additional operational recipients.

Active email contacts belong to the current workspace, are limited by dynamic entitlement, and can be assigned to monitors.

Workspace membersPingBeacons

Current workspaceExample OperationsSwitch

AOAlex O.Workspace memberOwner

SKSam K.Workspace memberAdmin

JRJordan R.Workspace memberOperator

MTMorgan T.Workspace memberViewer

03Incident context

Keep the notification tied to the event lifecycle.

Opening and recovery events remain connected to the monitor and incident record rather than becoming isolated messages.

Incident lifecyclePingBeacons

14:02Healthy request

14:04Failed check

14:04Incident opened

14:05Notification sent

14:08Recovery recorded

Start with PingBeacons

Route operational events without inventing another workflow.

Use email contacts and the in-app inbox for the failure, recovery, and SSL events PingBeacons supports.

Start monitoring Explore features