Find out whether a failing browser check is affecting real users without leaving Synthetic Monitoring. Browser checks already link each run to its Grafana Cloud Frontend Observability session. The new Real user context tab in the Timepoint Explorer builds on that link and compares the run with what your real users experienced around the same time.
The Real user context tab is available in experimental status. It’s under active development, and we’d love to hear what you think through the feedback widget in the panel. Linking a run to its frontend session works as before.
How it works
For each browser check run with a Frontend Observability session, the tab answers three questions. Was there a new deploy? You see the app build the run hit, when that build went live, and whether real users are on the same build or the check was served a different one. Are real users hitting the same failure? For each JavaScript error and failed request in the run, you see how many real-user sessions hit it in the hour before, and when it started. How are real users doing on the pages this run visited? You see sessions per page and the share with JavaScript errors.
The Explorer timeline also marks each new app build, so you can line up a deploy with the first failing or first passing run. Real users are Frontend Observability sessions that weren’t created by k6, so your checks and load tests are left out of the numbers.
Getting started
Open a browser check that tests an app instrumented with Frontend Observability, select a run in the Timepoint Explorer, and open the Real user context tab.
/)