What is browser monitoring?
Browser monitoring, often called synthetic monitoring, runs a real web browser against your site on a schedule and does what a customer would: opens the page, waits for it to finish loading, and clicks, types and checks the result. If any part of that stops working, you hear about it before your customers do.
It complements uptime checks rather than replacing them. A website check fetches a page's HTML in a fraction of a second and is right for most pages. A browser check takes a few seconds, but runs the page's JavaScript and can interact with it, so it sees problems a plain HTTP check can't.
What it catches that uptime checks miss
Most modern sites build their pages in the browser. The server answers 200 with an empty shell, and the content arrives through JavaScript. If a script fails to load, an API call breaks or a deploy ships a bug, the page is blank for visitors while every HTTP check stays green. A browser check looks for the text after the JavaScript has run, so it notices.
The same goes for flows. A login form can return 200 and still reject every password; a checkout can load and then fail on the payment step. A browser check that signs in with a test account and expects the dashboard, or adds an item to the cart and expects the total, catches exactly the failures that cost the most.
When a check fails
The alert names the step that failed and why, such as 'Step 4 (Click text=Sign in): not found or not ready within 15 seconds'. On the monitor's page you'll find every run with its step timings, a screenshot of what the browser saw, the JavaScript errors on the page and the requests that failed, so you can tell a changed button from a broken backend without reproducing it yourself.
Browser checks are re-run once before they count as down, so a single slow load doesn't page anyone. Failures open incidents and reach every alert channel, SMS and calls included, and the check can appear on your status page like any other monitor.
Safe by design
Steps are actions you choose from a list, not code, so a monitor can't run anything else in the browser. Each run gets a fresh private session, and the browser can only reach public addresses. Passwords marked Secret are stored but never displayed again, and never shared with the AI assistant.

