Plan synthetic monitoring for my key flows
Plans scripted synthetic checks for the key flows of a site you own, with intervals, locations, alerts and test accounts.
Task:
Plan the synthetic monitoring checks that tell me when a key flow on my site stops working.
Context:
My site is [site type] on [stack] and its most important flows are [list of flows, such as sign-up, search and checkout]. My users are in [regions]. I have [budget] a month and [number of people] people on call.
Rules:
- Choose at most 5 flows to script, ranked by what a failure costs, and give each a check interval and a pass condition that proves the flow worked, not only that the page loaded.
- Say from which regions to run each check and how to avoid a false alarm from one failed run.
- Use a dedicated test account with minimal rights and a safe test action, and keep its password out of the scripts and out of this chat.
- Give alert rules with who is told, how fast and how a recovery is announced.
- Run checks only against my own site and keep their load small.
Result:
A table with the columns flow, interval, pass condition, regions and alert, at most 5 rows, followed by 3 lines on how to keep the scripts up to date.