Browser checks
Check a sign-in, form or another browser journey and understand its step results.
On this page
What you need
Use an approved public target and a dedicated test account if the journey needs sign-in. You need permission to edit the workspace.
How to do it
- Choose Add monitor → Websites & applications → Browser check. Enter a name and the starting URL.
- Choose the supported locations and browser engines offered in the form. Set the interval and review the estimated usage.
- Add a small sequence of steps and an explicit expected result. Use protected-value fields for credentials instead of ordinary text.
- Review the setup, save it and inspect its first result. Enable only the alarm suggestions you want.
Good to know
Screenshots and traces start disabled. Enable them only after reviewing and explicitly approving the content to be recorded. Their retention is limited. A missing observation or unavailable checking capacity is unknown, not proof of a website failure.
If something goes wrong
Open the monitor overview and identify the failing step. Check its selector, expected result and permitted target. If a location is unavailable, wait for a current result before treating the target as recovered.
Related guides
- Choose a monitor type
Choose a monitor that matches the source of your data.
- Monitor a website or HTTP API
Check your website or public API for availability, response time and certificate expiry.
- Set up alarms and notifications
Choose meaningful alarm conditions, connect destinations and understand incidents.