Communicate
Alerts, dashboards, and status pagesEdit
Keep your team informed when issues occur and communicate service status to your users. Supercheck provides multi-channel alerting for internal teams and public status pages for external communication.
Core Features
Dashboard
View project health, recent runs, and monitor status at a glance
Alerts
Get notified via Slack, email, Discord, Telegram, Microsoft Teams, or webhooks when tests fail or monitors go down
Status Pages
Create public-facing pages to communicate system health, incidents, and maintenance to your users
Alert Providers
Send notifications through multiple channels. Configure different providers for different severity levels or teams.
Professional HTML emails via SMTP with detailed status information and dashboard links
Slack
Send alerts to the channel configured by your Slack webhook.
Webhook
Send JSON to a publicly reachable endpoint; use templates for PagerDuty, Opsgenie, or custom integrations.
Telegram
Bot messages to chats or groups with Markdown formatting
Discord
Embedded messages to server channels with color-coded status
Microsoft Teams
Adaptive Card notifications via Power Automate workflows
Smart Alert Thresholds
Choose failure and recovery thresholds to avoid notifications for brief interruptions. This example uses a failure threshold of 3 and a recovery threshold of 2.
| Check | Status | Failure Count | Alert? |
|---|---|---|---|
| 1 | ❌ Fail | 1/3 | No |
| 2 | ❌ Fail | 2/3 | No |
| 3 | ❌ Fail | 3/3 | Yes - Failure Alert |
| 4 | ✅ Pass | 1/2 successes | No |
| 5 | ✅ Pass | 2/2 successes | Yes - Recovery Alert |
Recommended settings:
- Failure threshold: 2-3 — Balances speed vs. false positives
- Recovery threshold: 2 — Confirms service is truly stable
Public Status Pages
Communicate service health to your users with branded status pages:
- Component Management — Organize services with individual status tracking and linked monitors
- Incident Workflow — Investigating → Identified → Monitoring → Resolved
- Scheduled Maintenance — Publish planned-downtime updates and change their status as work progresses
- Subscriber Notifications — Email, Slack, and webhook updates for incidents and status changes
- Custom Branding — Match your brand with logos, colors, and custom domains
- 90-Day Uptime History — Visual uptime charts for transparency
Use Cases
For Internal Teams
- On-call alerts — Route critical failures to Slack and PagerDuty
- Job results — Send email notifications for the job outcomes you enable
- CI/CD notifications — Webhook integration with build pipelines
For External Users
- Service status — Public page showing current system health
- Incident updates — Real-time communication during outages
- Maintenance windows — Advance notice of planned downtime
- Subscriber notifications — Send incident updates when Notify subscribers is selected.