Blog
Notes on planning work, catching errors and watching uptime, for solo developers and small teams.
-
A heartbeat alert has arrived: what to check when a cron job checks in late
A late check-in alert means a job did not report success in time. Here is how to work through the four checks that find the cause, in order.
-
How many failed checks before an alert? Setting a failure threshold on a monitor
What a failure threshold does on an AperioFlow monitor, a worked example, starting points by page type, and a checklist for your first 10 monitors.
-
How an HTTPS monitor warns you before a site's certificate expires
Learn how an HTTPS monitor checks your site's certificate and warns you at 30, 14 and 7 days before it expires, so renewal is never a surprise.
-
An alert rota for a small team: who gets the message this week
A simple weekly alert rota for a small team: one owner per week, a short first-steps list, a handover note and one noisy alert fixed each week.
-
Heartbeat monitor for a job that sometimes runs long: setting the expected interval
How to set the expected interval on a heartbeat monitor for a job that sometimes runs long, with a cron example and a checklist for late pings.
-
Where should an alert go? Email, web push and webhooks for a small team
Email, web push or webhooks: how a team of three can route monitoring alerts so the right person sees them, and a backup sees them too.
-
How often should an uptime monitor check? Choosing a check interval for a small site
How often should an uptime monitor check? A plain guide to choosing a check interval for a small site, with a worked example and a first-week review.
-
SSL certificate expiry alerts: a plain-English guide
How SSL certificate expiry alerts work, why an expired certificate stops visitors, and how to set up a reminder before the date passes.
-
Backup monitoring heartbeat: a plain-English guide
A plain-English guide to backup monitoring heartbeats: how they catch silent cron job and backup failures, and how to set one up in AperioFlow.
-
A status page for your client sites: what freelancers and small agencies should publish
A public status page for client websites: what freelancers and small agencies should show, what to write during an outage, and who reads it.
-
How Tweed Tyne runs its own work on AperioFlow
How the Tweed Tyne team uses AperioFlow day to day: what we track, which monitors and heartbeats we keep, and what we are not claiming.
-
Flat price or per seat: how a small team can work out what its tools cost
Work out what your team really uses each week, then compare per-seat fees with a flat monthly price for up to 10 people.
-
Writing tasks small enough to finish: a habit for teams of two to ten
How to write small tasks for a team: size work to finish in a day or two, give each one a single owner and a clear done line, and check sizes weekly.
-
Slow is not down: choosing a response time to alert on
How to pick a website response time threshold for alerts: measure normal first, wait for repeated slow checks, and keep slow-page warnings apart from outage alerts.
-
Which errors to fix first: a simple way to triage a pile of them
A four-question method for triaging application errors: count users, check sign-in, payment and saving, check releases, then decide and assign one owner.
-
On-call for a solo developer: how to be the person who gets the message without burning out
How a solo developer can cover on-call without burning out: decide which alerts wake you, batch the rest into a morning check, and retune noisy alerts weekly.
-
How to monitor client websites as a freelancer without checking them by hand
Set up one monitor per client site, pick what to check, and tell clients what happened in plain words. A practical routine for freelancers who run client sites.
-
Post-incident review template for a small team: what to write down once it is fixed
A short post-incident review template for small teams: what to record once the fault is fixed, how you found it, and who owns the follow-up.
-
A health check endpoint for your web app: what it should return
What a health check endpoint should return, which status codes to use, what to leave out of the response, and what to alert on.
-
What to put in your first 10 monitors on a small team
Ten monitors cover most small web apps: home and sign-in pages, your API, the form people pay through, backups, cron jobs and certificate expiry.
-
Website uptime monitor with alerts: a plain-English guide
A plain-English guide to website uptime monitors with alerts: what they check, what to alert on, and how to set one up for your own sites.
-
Uptime monitoring for small teams: a plain-English guide
What uptime monitoring does, what a small team should alert on, and how to set it up in an afternoon, with a Free plan to start.
-
Monitoring a self-hosted web app on a small server: what to check first
Three checks to add first when you monitor a self-hosted web app on a small server, and how to keep alerts within your own team.
-
What to alert on for a small web app: a short list that will not wake you for nothing
A short decision list of what to alert on for a small web app: site down, slow responses, certificates, missed heartbeats and new errors, plus what to leave out.
-
Catching errors before your users report them: a small team's first-hour setup
Set up error alerts in your first hour: what to send, how to alert on new errors only, who gets the email, and how to turn a fix into a task.
-
A small team's weekly planning habit: one list, one owner, one review
A simple weekly planning habit for small teams: one list, one owner per task, and a short review that catches what slipped or broke.
-
Incident update template: five lines to send while you are still fixing it
A copy-and-paste incident update template with five lines, a worked checkout example, and how the wording changes as the incident moves on.
-
One tool for tracking work, errors and uptime: a week in the life of a small team
How a small team can use one tool for tasks, error groups and uptime checks across a working week, with a habit list they can copy.
-
Free viewers for clients: let people see a project without paying for a seat
How a read-only viewer lets clients follow a project, what they can and cannot change, and how viewers relate to the Team plan price.
-
Certificate expiry monitor: what to check, how early to warn and who gets the alert
Set up a certificate expiry monitor with warnings at 30, 14 and 7 days, clear ownership and a short renewal checklist for your team.
-
Export your project data: how to keep a copy of your own work
How to export your project data from AperioFlow, when to download it, and how to check the file opens and looks right. Start free today.
-
Website uptime monitor with alerts: what to set up on day one
Set up a website uptime monitor with alerts on day one: pick the pages to watch, set the check interval, choose who gets the alert, and copy a short checklist.
-
Second location uptime check: how to tell a real outage from a network blip
A second location uptime check confirms a failure from another place before it wakes you. Here is how to set retries, timeouts and alerts that you can trust.
-
Read-only client access to a project: share progress without giving away the keys
Give clients read-only access to a project so they can see tasks and progress without changing anything. Set it up on the free plan in minutes.
-
Building AperioFlow in public: one tool for tracking work, errors and uptime
AperioFlow puts tasks, errors, uptime and status pages in one place. See what works today, how Tweed Tyne uses it, and how to download your data.
-
Coolify uptime monitoring: watching apps you host yourself
Coolify uptime monitoring: check each app URL from outside your server, add heartbeats for cron jobs and backups, and know what to alert on first.
-
A project and task tracker for developers: track work as a small team
How a team of two to ten developers can track work with a short list, a 20-minute weekly plan and tasks tied to the errors that create them.
-
Scheduled maintenance notice example and how to tell customers about downtime
A scheduled maintenance notice example you can copy, plus how far ahead to give notice and how to word downtime updates for your customers.
-
Error tracking for small teams: group repeated errors into one issue
See how error tracking for small teams works when repeated errors are grouped into one issue you can count, read and act on.
-
How to write an incident update: a plain template you can copy
A plain incident update template for status pages: the four stages, what each update must say, example wording and words to avoid.
-
How to tell customers about downtime: a status page for a small SaaS
How a small SaaS can run a status page customers trust: what to show, how to word a first notice, and how to keep the page current.
-
A status page for a small SaaS: what to put on it and how to keep it honest
How to set up a status page for a small SaaS: what customers look for, how to name components, and how to keep updates and incident history honest.
-
SSL certificate expiry alerts: stop a lapsed certificate taking your site down
How SSL certificates expire unnoticed, what visitors see, and how to set expiry alerts at 30, 14 and 7 days so renewal never catches you out.
-
Backup monitoring with a heartbeat: knowing when last night's backup did not run
Set a heartbeat on your backup job so you hear about it when last night's backup does not run. A simple check for solo developers and small teams.
-
How to write an incident update: a plain template for small teams
A plain template for incident updates on a live site: the four statuses, what each update must say, and a worked example for small teams.
-
How to monitor a cron job with a heartbeat: a step-by-step example
A hands-on walkthrough: create a heartbeat, add a ping to your crontab line, test a failure on purpose, and read the alert when it fires.
-
What a heartbeat monitor is for: watching cron jobs and backups
A heartbeat monitor alerts you when a cron job or backup stops checking in. How it works, how to set the grace period, and how to start free.
-
Uptime monitoring for small teams: what to check and when to alert
A practical guide to uptime monitoring for small teams: which pages to check, how often, when to alert, and who gets the message.
-
Telling customers about maintenance before you take something down
How to tell customers about planned maintenance: what to include, when to post it, how to send a reminder and what to do if the work overruns.