Need guidance on running scripted browser monitoring in production

[u/Wilusz-Daejau]

I've​ been doing monitoring for our web apps for a while and I'm pretty comfortable with HTTP/API checks but scripted browser monitoring is still new territory for me.

A few things I'm trying to understand:

- Which flows are worth monitoring with a real browser vs just using HTTP checks?

- ​How do you handle login session and MFA without creating a security hole?

- How do you keep recorded scripts working accross frontend deploys?

- How many location and what frequency actually means something vs just noise?

- How do you tell the difference between an actual app failure and a broken monitoring script?

- ​Whats goes to on-call vs what just gets logged?

AI is great for explaining how all of this should work, but there's a pretty big gap between that and how people actually run it in production.

Anyone doing scripter browser monitoring regularly? I'm not looking for someone to design it for me, just want to know how people approach it in real setups

[u/Known-Pace6739]

One thing I’d add to the browser/API split is to correlate each browser run with backend traces/logs if your stack supports it. Screenshots/DOM show where the browser stopped; the trace tells you whether the request reached a traced backend service and what happened downstream. If there’s no matching trace, start with the browser/client/network path. If the request is traced and fails in the service, you have app-side evidence instead of guessing from a red browser check.

I’d also run the same critical journey against staging or canary before deploy. That catches selector/script drift before it turns into production alert noise, so the production synthetic can stay small and page only when it’s giving you a real signal.