How Sandglass Works
Sandglass is built to be simple on day one and powerful as you grow. Here is the reliability workflow from first monitor to published status updates.
Your reliability flow
Add your first monitor
Define what to watch, where to run checks from, and how often to verify health.
Add a URL or service endpoint.
Choose regions and protocol.
Set the check interval and threshold.
Detect and validate incidents
Sandglass confirms outages with retries and multi-region checks before alerting.
Noise reduction with smart retries.
Regional confirmation on failures.
Instant visibility in dashboards.
Alert the right people
Notify responders by email, Slack, or webhooks with clear severity.
Route alerts by monitor or team.
Escalate when incidents persist.
Keep updates aligned across channels.
Share status externally
Publish a status page with live uptime, response time, and incident context.
Choose what services are visible.
Customize branding and layout.
Keep customers informed automatically.
Learn and improve
Turn incidents into insights with timelines, reports, and reliability trends.
Review MTTR and failure patterns.
Export reports for stakeholders.
Refine thresholds over time.
From signal to story
Every check flows into alerts, incident response, and reporting without extra tooling.
Monitor
Scheduled checks keep an eye on health.
Detect
Retries and regions validate failures.
Alert
Notifications route to the right channels.
Resolve
Incident timelines guide response.
Report
Uptime and SLA dashboards stay current.
A real incident, captured end-to-end
A checkout API fails at 02:14. Sandglass detects the error in two regions, alerts the on-call team, and creates an incident timeline with response time context and uptime impact.
Incident timeline snapshot
02:14
API check fails in us-east
02:15
Retry confirms failure in eu-west
02:16
Slack + email alerts dispatched
02:20
Status page updated automatically
What happens next
Once monitoring is live, Sandglass keeps your team in the loop with reporting and continuous insights.
Uptime reports
Share weekly and monthly summaries with stakeholders.
SLA tracking
Keep reliability targets visible with live SLA dashboards.
Status updates
Public pages stay accurate without manual edits.
Common questions
Start with a single monitor
Spin up your first check, then expand into alerts, dashboards, and status pages.