Alerts and notifications

Alerts collects conditions that need attention. Notification destinations send those changes to the channels your team uses. The recorded condition and the message delivery are separate facts.

Set up a destination

Open Notifications as an account owner or admin. Choose the supported destination, enter its details, and complete its test before enabling delivery.

Slack and Discord are available for chat notifications. Generic webhook receivers use signed messages; follow the webhook setup guide before connecting your receiver.

Keep destination URLs and signing secrets private. Use the application's generated setup details and do not paste credentials into documentation or support messages.

Read an alert

Start with the affected project or host, the condition, and its last observation. Check whether the underlying signal is fresh. An observer that stopped reporting requires a different investigation from an HTTP endpoint returning errors.

Follow the linked resource to inspect evidence and recent activity. Recovery means the relevant condition cleared under its own rules; it does not prove every part of the application is healthy.

Understand deploy messages

Enabled chat destinations can receive deployment-start and terminal outcome messages. A needs-attention deployment carries its attention details in the outcome message rather than sending a second opening message for the derived verification alert.

Owners and admins can choose deploy outcome email preferences in their account settings. Members do not receive those owner/admin deploy emails.

Check delivery history

Upstate records delivery outcomes independently of the alert. A retrying or failed delivery does not mean the underlying alert disappeared.

Provider acceptance means the destination accepted the message, not that a person saw it. Review visible failure details, retest revoked or changed credentials, and confirm that the destination is enabled for the intended account.