Skip to content
GDPR compliant. Hosted in DE.
14-day free trial →
Module · XICTRAQ

Synthetic monitoring with Playwright

Real browsers click through your critical flows: login, checkout, form. Chrome Recorder import, multi-step scripts, screenshot per step — alert on every break.

from Business plan
No credit card Servers in Germany 3 EU probe nodes 14-day pro trial GDPR compliant
Live status
Synthetic monitoring with Playwright
ACTIVE
Real Chromium browser
No HTTP mock — real Playwright with full JavaScript, cookies, localStorage. If the browser can do it, the monitor can — including React/Svelte/Vue SPAs.
11 step types
goto, click, fill, type, wait_for, wait, assert_text, assert_url, assert_status, assert_visible, screenshot. Up to 40 steps per scenario — for login, cart, checkout, form flows, SPA routing.
Flexible interval
5 minutes, 15, 30, 60, 180 or 720. Run-now button in the dashboard for an instant check after a deploy.
Failure screenshot
Every failed step automatically captures a screenshot at the moment of failure and stores it with the run, available in the run detail. You see exactly what the browser actually saw.
Last check just now
What it does

Uptime monitoring says: “Homepage returns HTTP 200”. That does not protect you from a broken login, a checkout that hangs after step 3, or a contact form with the wrong server response. Browser monitoring drives a real Chromium browser (Playwright) through your scenario: open page, click, fill, wait for element, assert text or URL, take screenshot. When a step breaks — selector missing, error text shown, wrong redirect — you get an immediate alert with error message and step number; the failure screenshot is in the run detail.

Synthetic monitoring with Playwright features

Real Chromium browser

No HTTP mock — real Playwright with full JavaScript, cookies, localStorage. If the browser can do it, the monitor can — including React/Svelte/Vue SPAs.

01 / 06

11 step types

goto, click, fill, type, wait_for, wait, assert_text, assert_url, assert_status, assert_visible, screenshot. Up to 40 steps per scenario — for login, cart, checkout, form flows, SPA routing.

02 / 06

Flexible interval

5 minutes, 15, 30, 60, 180 or 720. Run-now button in the dashboard for an instant check after a deploy.

03 / 06

Failure screenshot

Every failed step automatically captures a screenshot at the moment of failure and stores it with the run, available in the run detail. You see exactly what the browser actually saw.

04 / 06

Run history with step timings

Per run: total duration, duration per step, success/failure. Detect slow creep on one specific step long before the whole flow breaks.

05 / 06

Alert on all channels

Email, Slack, Discord, Teams, Telegram, webhook — the exact same alert engine as uptime. With dedupe, ACK button, escalation and postmortem export.

06 / 06
Process

How it works

1

Build the scenario in the dashboard

Step by step: open page, click CSS selector, fill a field, wait for an element, assert text or URL. No code — just the builder.

2

Pick an interval

Every 5 to 1440 minutes. Each run opens a fresh browser instance from our EU data centre — without polluting real-user analytics.

3

Alert on failure + screenshot

When a step breaks, the alert arrives immediately with step number and error message; the run detail shows the failure screenshot. You see exactly what the browser saw.

FAQ

Frequently Asked Questions

Can I log in without storing my password in plain text?
Yes. Values of fill and type steps, such as a password, are stored encrypted and are not shown again in the editor; they are only decrypted for the run. For production logins we still recommend a dedicated "monitoring account" with restricted permissions, not your admin account.
How does the monitoring affect my analytics?
Not at all. The runner automatically blocks our own tracker (`t.js`, `/api/p*`) so test-run pageviews do not pollute your analytics dashboard. It also sends a dedicated user agent (`XICTRAQ-BrowserMonitor/1.0`) that your own analytics tools can filter out.
What happens when a step flaps (sometimes works, sometimes not)?
Alerts dedupe per flow (10-minute window by default, configurable) so flaky selectors do not cause an alarm flood. For recurring flaps, check the run history — it is usually a front-end race condition that a `wait_for` before the next step fixes.
Can I upload files or test downloads?
Neither is in the builder yet, but both are on the roadmap. Short-term: you can POST a script JSON via the API. Ping us if you need it now.
Which location runs the monitors?
Currently one German data centre (DE-1). Multi-region is planned once the baseline is stable — target is parity with uptime monitoring (three distributed EU data centres, two in Germany and one in Finland, 2-of-3 consensus).
From which plan is browser monitoring available?
Included from the Business plan (€29/month, cancel monthly) onwards. No additional per-run charge.
Start in 60 seconds

Let XICTRAQ watch your website.

Permanent free plan available. No credit card, no installation, no hidden fees.