Configurable schedules Planned
Will run a scenario every minute, every five minutes or hourly, with different cadences for different criticality.
Monitoring · Planned
Know it broke before your customers tell you.
Monitoring is designed to run your customer journeys around the clock from the UK and the EU. When a page slows past your limit or a step fails, the alert will arrive with the video and logs of the exact run that caught it, so your team will debug the incident instead of hunting for it.
Monitoring is on the roadmap behind Testing Suite, now in early access. Same scenarios, run continuously.
What it does
Synthetic monitoring, with the report attached.
Most synthetic monitoring tools tell you a page took 3.2 seconds to load. Then you go to find out why. Open a different tool. Look at RUM samples. Cross-reference with deploy times. Eventually find that a third-party tag started timing out.
Monitoring in Evaluat will run your scenario in a real browser every N minutes, from a chosen region. When the run fails, or LCP regresses past your threshold, the alert will come with the session video, the network log, the console log, and the step playback for the run that triggered it, so you will debug the incident from one page.
Same scenarios you use for performance tests. Same configuration UI. Same report. Different schedule and concurrency. Build once.
What an alert looks like
The alert will be the debug session.
The plan is a Slack message like: "LCP on /product/SKU-12345 regressed from 2.1s to 3.8s on the EU monitor at 14:22 UTC. View session."
Click through, and you'll land in the session report for the run that triggered the alert. Video. Network. Console. Step playback. The third-party tag, the slow database, or the broken deploy. It will already be there.
Roadmap
What's planned.
Rough shape of what Monitoring will ship with. Subscribers get an email when each piece is usable.
Multi-region runs Planned
Will run the same scenario from the UK, the EU and the regions we add next, so you will be able to compare what users see in different geographies.
Threshold alerts Planned
Will alert when LCP, INP, CLS or a custom step duration crosses your budget, with the session attached for debugging.
Slack & PagerDuty Planned
Alerts that will land in the right channel, with links to the failing session video and step playback.
Trend dashboards Planned
Long-term Web Vitals trends per scenario and per region, so you will be able to spot the slow regression that aggregate RUM misses.
Public status feed Planned
An optional public status page that your monitors will feed. Customers will see real performance, not "all systems operational."
What teams use it for
Six monitoring patterns we hear on demo calls.
Reasons to point a continuous real-browser monitor at your critical journeys once Monitoring ships. Every alert will carry the session.
Regional baselining
The same checkout monitor will run from the UK and the EU, to catch the latency that only customers in one region see.
Slow regressions
Aggregate RUM hides the 200ms LCP creep across a month. A continuous synthetic monitor will show it, with the session video for each data point.
Step-level failure alerts
When the login step starts failing because a CDN-cached asset went 404, the alert will name the step and link the session. No more "site is down" pages.
Third-party watchdog
A monitor will watch the third-party tags you embed and alert when, for example, an analytics SDK starts adding noticeable delay to a page.
Public status fact-check
Don't say "all systems operational" when a customer can't complete checkout. Your status page will be able to show monitor results, not vibes.
Deploy-correlated alerting
When a Web Vital crosses the threshold within minutes of a deploy, the alert will link to the regression candidate. Cause and effect, attached.
Common questions
Monitoring, answered.
What is Evaluat Monitoring?
Monitoring is a planned product that will run your customer journeys around the clock in real browsers, on a schedule, from the UK and the EU. When a page slows past your limit or a step fails, the alert will arrive with the video and logs of the exact run that caught it.
How will Monitoring differ from real user monitoring (RUM)?
RUM samples what already happened to your visitors and aggregates it, which hides slow creep. Monitoring will be synthetic, running the same scenario continuously under controlled conditions, so a gradual LCP regression will show up as a trend, with a session video behind each data point.
Which regions will monitors run from?
The UK and the EU, the same regions Performance Testing runs from today. Multi-region runs of the same scenario are planned, so you will be able to compare what users see in different geographies.
When is Monitoring coming?
It is on the roadmap behind Testing Suite, which is now in early access, and will reuse the same scenarios and configuration UI. Monitoring is planned. Join the design-partner waitlist. We email the waitlist when each piece is usable.