Watch the public journey
Monitor home, pricing, checkout, login, and help pages so visible breakage appears on the board before customers report it.
Uptime and content monitoring
Monitor the pages, redirects, APIs, and dependencies customers actually hit.
Dashy turns uptime, response time, redirects, expected content, heartbeat pings, single-service TCP port checks, JSON contracts, third-party dependency status, and certificate windows into scheduled dashboard checks.
Service board
customer paths
Homepage186ms200 ok
Checkoutslow1.9s response
Contentmatchpricing text found
Cronfreshheartbeat 4m ago
SMTPopentcp 587 reachable
Redirect5 hopsloop risk
JSON APIschemafield missing
- Intervals
- 5m to monthly
- Evidence
- Status and body hints
- Alerts
- Warning before critical
Scan
Inspect the public URL for status, response time, redirects, content type, and certificate state.
Classify
Separate hard downtime from slow responses, content misses, redirect drift, and contract changes.
Save
Turn the useful findings into scheduled dashboard checks with sensible warning and danger thresholds.
Show
Publish the same signals to private boards, public status pages, fullscreen displays, and reports.
Dashboard components
The basic checks still explain most visible failures.
- Availability
- HTTP status, response time, final URL, content type, TLS state, and threshold-based warnings.
- Content
- Required text, missing text, regex checks, stale pages, and release mistakes customers can see.
- Heartbeat
- Cron jobs, imports, backups, and internal services ping a private URL so Dashy can show last signal age.
- TCP ports
- Known service ports such as SMTP or a controlled gateway are checked one at a time, never as broad scanning.
- Routing
- Redirect chains, unexpected destinations, too many hops, and path-specific failures after site changes.
- Contracts
- JSON response shape, expected fields, third-party dependency status, and API health evidence.
Evidence boundary
Keep public checks useful without turning them into data capture.
Uptime and content checks should explain visible customer impact while avoiding private pages, credentials, and sensitive response detail.
- Public targets
- Checks run against operator-approved public URLs, redirects, status codes, expected text, content type, and safe JSON fields.
- Retained evidence
- Dashy stores final status, response time, final URL, redirect count, matched or missing content state, and contract pass/fail results.
- Private detail
- Raw response bodies, credentials, session pages, private account paths, and sensitive payloads stay outside public dashboard output.
- Shared output
- Public boards and reports should show state, timing, route drift, content mismatch, and safe hints that help teams act quickly.
Separate slow from down
Show response-time warnings, hard failures, content mismatches, and redirect issues as different states instead of one vague outage.
Keep APIs and dependencies honest
Track JSON shape, dependency status pages, and route-level checks beside SSL, DNS, and public status output.
Scan public paths once, then save the checks worth repeating.
Uptime, redirect, content, heartbeat, TCP port, JSON contract, dependency status, and SSL tools can inspect or create the first signal immediately. Quick start turns useful findings into scheduled dashboard components.