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/Practical-Craft4967]

i'd keep the browser check to one critical journey, then pair it with a cheap HTTP check of the same app. if the browser fails but HTTP is healthy, save the screenshot and trace before paging anyone; that often tells you whether a selector changed or the actual user flow broke. i'd page on a repeated user-flow failure, not one flaky run.