# Need guidance on running scripted browser monitoring in production — retained record

> Retained reddit record from reddit:devops.

Canonical: https://highsignal.app/data/records/1d2aa22e34bc5135

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:devops)  published 2026-09-29 04:44 ingested 2026-09-30 02:39

[original source ↗](https://www.reddit.com/r/devops/comments/1wt0v99/need_guidance_on_running_scripted_browser/)

## retained text



```
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
```



document fetched 2026-09-30 00:26 · canonical https://reddit.com/r/devops/comments/1wt0v99/need_guidance_on_running_scripted_browser
