I’ve been working on a browser automation project around a problem I’ve run into with website monitoring.

A website can be completely online and responding normally, while something important for users is broken. For example, a login might fail, a checkout button might stop working, or a form might no longer submit.  
My approach is to have an automated browser actually go through these journeys instead of only checking whether the site responds.

The video shows the current journey-building process. You can define a sequence of actions and then have the browser replay it automatically.  
At the moment I’m testing things like login, signup, checkout, booking and forms. When a journey fails, I’m capturing the failed step, screenshots and the timeline so there’s some context around what happened.

I’m also experimenting with using AI to analyse the failure and explain what might have gone wrong.  
I’m interested in how other developers handle this problem today. 

Do you normally use synthetic monitoring, Playwright/Cypress tests, custom scripts, or something else?  
I’m especially interested in where browser-based monitoring becomes useful and where it becomes more trouble than it’s worth.  
Would be interested to hear how people here approach it.

I’ve been experimenting with browser automation for monitoring customer journeys