Kept for existing links. Monito runs plain-English end-to-end browser tests.

Incident management, and a status page of checked journeys

Detect, tell people, write down what happened. A Monito status page reports scheduled checks. It is not your pager, and it is not a user session.

incidentsstatus-pages

An incident practice is three habits. Notice that something people need is broken. Say so, in one place, while it is broken. After it is over, write what happened and what you will change. The tool is secondary. A channel nobody reads is not a practice.

Monito is not that practice. It does not page you, it does not record your users' sessions, and it does not write the postmortem.

What a Monito status page is

Status pages need Pro. You name journeys ("sign in", "check out") and attach the tests that prove them. The page shows whether those journeys passed the last check that counts.

Only scheduled runs and deploy-webhook runs count. A check you start by hand, a CI run against a preview, and a retry do not move the page. The first public failure is confirmed by one extra run (1 credit) unless you turn that off. Monito's own failures — a timeout, a model error, lost evidence, a missing login — are a gap, not an outage. A run that got no answer from your site is not, by itself, "down." Probes decide that.

Visitors see journey names, states, times, and uptime. They do not see test instructions, screenshots, or credentials. You get an email when the page changes state.

How to put a check on a deploy and on a schedule is run checks on every deploy.

What to do with a failed check

Read the report. If the badge is Failed and the cause is an app bug, you have steps and evidence to paste into the tracker. Copy as issue. If the badge is Error, the check could not verify the scenario. That is not yet an incident. What cannot verify means.

Sign up to run the first scenario. The status page comes after you have a schedule worth publishing.

Related posts

Compare Monito with other tools