Synthetic Monitoring Plan
Probe critical journeys from the outside.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Plan synthetic monitoring for my site or API. Critical journeys: [CRITICAL_JOURNEYS]. Regions where users are located: [USER_REGIONS]. Authentication needs: [AUTH_NEEDS]. Existing monitoring: [EXISTING_MONITORING]. Define the probes: for each journey the steps, the assertions (status, content, timing), the frequency, locations, and failure criteria such as two consecutive failures from two locations. Use test accounts and data that cannot touch real customers, and say how to protect the test credentials. Include a plan to keep probes from distorting analytics or triggering fraud systems. Provide a table of probes with alert severity and runbook link placeholders. Add maintenance guidance for updating probes when pages change and how to treat planned downtime. Estimate the monthly probe count and cost with placeholders. Add a section on interpreting results: how to tell a real outage from a probe failure, what to compare against real user monitoring, and how to avoid alerting during known maintenance. Provide a template for the first-line response when a probe alert fires, including the three checks to run before waking anyone else, and a quarterly review of whether the probes still match real journeys.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.