Watch important pages
Keep pricing, landing, contact, and campaign pages visible when a release changes content or layout unexpectedly.
Visual monitoring
Catch visible page changes that status codes miss.
Dashy packages screenshot snapshots, content-change checks, expected text, and visual evidence as capacity-gated monitoring for important public pages.
Visual board
page evidence
changed
- Screenshot
- Snapshot saved
- Content
- Expected text
- Runtime
- Capacity capped
Start light
Use content and uptime checks first for public pages that only need text, status, or timing evidence.
Gate runtime
Reserve screenshot capture for paid capacity so browser checks stay predictable on the launch VPS.
Capture
Save screenshot evidence, content-change state, expected text results, and latest capture metadata.
Review
Show visual evidence beside uptime, SSL, DNS, redirects, and reports for important public paths.
Screenshot capture boundary
Use browser captures deliberately, then keep evidence scoped.
Visual checks are heavier than HTTP and content checks, so Dashy treats screenshot capture as controlled capacity with retained evidence rather than a default scan for every page.
- Public first
- Use uptime, redirect, content, and Core Web Vitals checks before adding browser-backed screenshots.
- Capacity gate
- Screenshot capture runs only when browser capacity is enabled and per-run limits keep the VPS predictable.
- Retained evidence
- Dashy stores screenshot files and capture metadata for the configured retention window, then cleanup removes old images.
- Shared output
- Public boards should show visual status and selected evidence only after the owner confirms the page is safe to display.
Dashboard components
Use visual checks for pages where appearance and content matter.
- Screenshot snapshots
- Capture a page image, save screenshot evidence, and show whether the latest capture changed.
- Content drift
- Track expected text, missing text, release mistakes, defaced pages, and stale public copy.
- Evidence panels
- Show operators the screenshot, payload, changed state, and latest capture metadata from check details.
- Capacity control
- Browser-backed checks stay plan-gated and capped so a single VPS remains predictable during launch.
Show client evidence
Add visual proof to client reports when the homepage is up but the page output has drifted from what was expected.
Pair visual checks with status
Use screenshots beside uptime, SSL, DNS, redirects, content, and transaction checks for higher-risk public paths.
Start with lightweight content checks, then add screenshots where evidence is worth the runtime.
Public content checks can inspect a page immediately. Screenshot monitoring is reserved for capacity-controlled scheduled boards.