Keep a history of checks
Every scheduled run is saved separately from the current status of the website.
Website monitoring and notification service
A service that checks websites on a schedule and tracks notification delivery.
Project overview
What the service does
A website-monitoring service that runs scheduled checks, records each run, and manages notification delivery as its own workflow. Operators can see the check result, retry state and queue delay instead of treating every issue as a single alert.
Operators need to see site-check results separately from notification delivery, including failed attempts and queue delays.
Who uses it
Website operations and marketing teams responsible for availability checks and notifications across multiple sites.
Input
- Website addresses, check types and schedules.
- Results from HTTP or browser checks.
- Notification recipients and delivery responses.
Output
- Timestamped check history and current monitor state.
- Persisted notification attempts with retry status.
- Queue depth and oldest-task delay for operators.
01 / How the service works
Site checks
Site checks
- INPUTSites and schedule
Choose addresses and check types
- PROCESSRun HTTP or browser checks
Record a separate result for every run
- CHECKUpdate current status
An old run cannot overwrite a newer result
- RESULTDeliver notifications
Show attempts, retries and queue delay
03 / Implementation details
Engineering decisions
Keep newer results current
A result from an older run cannot replace the status written by a newer run.
Track notification attempts
Operators can see notification status, retries and the age of the oldest queued task.
Software development for business
Have a project in mind?
Tell me what the application should do, how the team works today and which requirements or deadlines matter.