Synthetic Monitoring Design: Check User Outcomes, Not 200s

Q: What is synthetic monitoring?

Synthetic monitoring runs scripted checks against your product on a schedule, from chosen locations, to detect failures before or regardless of real user traffic. It is the black-box layer of observability: it tests externally visible behaviour as a user would see it. Checks range from simple HTTP requests to full browser journeys that sign in, search, add to cart and pay, asserting the outcome a real user would expect at the end.

Q: Why do synthetic checks pass during real outages?

Usually because they assert server responses rather than user outcomes. A 200 status and a fast load prove the server answered, but many outages happen after the HTML arrives: a failed third-party script, a broken bundle, a rejected session token at a later step, an empty search index or a stale CDN asset in one region. A check must assert the outcome, such as an order number appearing, to catch those failures.

Q: How many synthetic checks do I need?

Start from promises rather than URLs. Most products have five to ten journeys whose failure costs money or trust within the hour, such as sign-up, login, search, add to cart, payment and one or two core actions. Build one browser journey per promise, run it from regions matching your users, and add lighter API checks for the dependencies those journeys use so failures can be localised quickly.

Q: What is the difference between synthetic monitoring and real user monitoring?

Real user monitoring measures what actual users experienced, including devices, networks and long-tail paths you never scripted, and is the right place for Core Web Vitals at the 75th percentile. Synthetic monitoring tells you when a critical journey breaks even when nobody is using it, such as overnight, in a new region or right after a deploy. They are partners: RUM for breadth, synthetics for guaranteed coverage of critical journeys.

Q: How should synthetic monitoring alert?

Page on confirmed broken promises. A practical rule for browser journeys is to alert when the outcome fails in at least two locations on two consecutive runs, which filters single-runner glitches without much delay. Include the journey name, failing step, a screenshot and a link to the backend trace of the failed run. Record step timings as metrics and alert on trends, not on one slow run from one region.

Q: How do I correlate synthetic checks with backend traces?

Inject a W3C Trace Context traceparent header on every request the check makes, and mark the run as synthetic with a span attribute or baggage. Your OpenTelemetry-instrumented services will then continue the same trace, so a failed check links straight to the backend spans for that run. The marker also lets you exclude synthetic traffic from business analytics and from real-user performance dashboards.

Q: Will bot protection block my synthetic checks?

It may, and it should see them, because checks need to traverse your CDN, WAF and bot management the way real traffic does. Do not solve this by disabling protection for whole IP ranges, which creates an opening attackers can use. Use a signed header, dedicated test identities or a vendor-supported allow mechanism tied to the check, and keep those credentials in a secret store with regular rotation.

Q: How much does browser synthetic monitoring cost to run?

Cost scales with journeys multiplied by locations multiplied by frequency, and browser runs are much heavier than HTTP checks. Five journeys from four regions every five minutes is about 5,760 browser runs a day, which is usually reasonable. Two hundred journeys at the same cadence rarely is, and is rarely useful. Spend the budget on critical journeys at good frequency, and prune checks that protect no promise or are flaky.

Satyam Kumar

Back to Blog

architecture

Synthetic Monitoring Design: Check What Users Do, Not What Servers Return

By Satyam KumarOctober 25, 202611 min read

synthetic monitoring synthetic transaction monitoring browser synthetic checks black box monitoring playwright monitoring w3c trace context opentelemetry tracing real user monitoring core web vitals checkout monitoring status page accuracy sre alerting slo error budget api transaction checks multi region monitoring flaky check reduction

Synthetic Monitoring Design: Check What Users Do, Not What Servers Return

Frequently Asked Questions

Share this article

Twitter LinkedIn WhatsApp

Satyam Kumar

Founder & AI Architect, AppScale LLP

AI & Cloud Architect. Helping teams build systems that scale to millions.

LinkedIn GitHub

Synthetic Monitoring Design: Check What Users Do, Not What Servers Return

Frequently Asked Questions

Share this article

Comments

Leave a comment