StackPulse alerts turn check failures and recoveries into notifications your team can act on.
Email alerts
Email alerts send incident notifications to configured recipients.
Use email for:
- Primary operator inboxes.
- Shared incident aliases.
- Low-volume systems where email is still monitored.
Make sure the API has a valid Resend API key and sender address configured before relying on email delivery.
Discord alerts
Discord alerts send notifications to a webhook URL.
Use a channel that is visible to the people responsible for the monitored system. Avoid general chat channels where incidents will be buried.
Test notifications
Use the controlled incident test in Settings after changing destinations.
The test can verify:
- Email delivery.
- Discord webhook delivery.
- Resolution notifications.
- Delivery history records.
Delivery history
Delivery history records what StackPulse attempted and what happened.
| State | Meaning |
|---|---|
sent | The provider accepted the notification. |
failed | StackPulse tried to send but the provider rejected or failed the request. |
suppressed | Delivery was intentionally skipped because alerts were disabled or not configured. |
pending | A delivery record exists but has not reached a final state yet. |
Misconfigured alert states
Common causes:
- Missing Resend API key.
- Invalid email sender domain.
- Empty recipient list.
- Discord webhook URL was deleted or rotated.
- Alerts are disabled for the current environment.
Alert settings are operational settings. Treat every sender, webhook, and recipient change like production configuration and test it immediately.