Catch checkout breakage
Track the public path from product or pricing page to checkout handoff so payment failures are visible quickly.
Transaction flow monitoring
Watch the journeys that turn outages into lost revenue.
Dashy packages multi-step public journeys, failed step evidence, final status, timeout windows, and display-board visibility as a higher-value Business component pack.
Journey board
business path
Step 1200pricing loaded
Step 2200checkout opened
Step 3500payment failed
Timeout12slimit exceeded
- Evidence
- Failed URL saved
- Gating
- Business pack
- Runtime
- Capacity controlled
Qualify
Start with uptime, content, SSL, DNS, and status checks before adding heavier journey runtime.
Model
Define the public steps, expected statuses, timeout window, failed URL evidence, and safe stop point.
Gate
Reserve transaction checks for Business boards with queued execution and capacity controls.
Review
Show passed steps, failed step, final status, timeout, and lost-revenue context on displays and reports.
Business component
Use transaction checks where a broken journey has direct cost.
- Critical paths
- Checkout, booking, login, onboarding, payment handoff, account creation, and lead forms.
- Step evidence
- Passed count, failed step, failed URL, final status, timeout, and plain-language dashboard guidance.
- Plan control
- Transaction flows stay gated separately from normal uptime, content, DNS, and status checks.
- Operations
- Higher-cost checks can be queued and capacity-limited so one VPS remains predictable during launch.
Runtime boundary
Run heavier journeys only when the value and capacity are clear.
Transaction checks should stay reserved for business-critical public paths with explicit steps, safe stop points, and owner-reviewed output.
- Public steps
- Flows model operator-approved public URLs, expected statuses, timeout windows, and non-sensitive handoff points.
- Capacity gate
- Business-plan queues and per-run limits keep browser or multi-step runtime from crowding normal uptime and SSL checks.
- Retained evidence
- Dashy stores passed step count, failed step, failed URL, final status, timeout, and observed duration for history and reports.
- Shared output
- Public boards should show journey status and failure context, while entered data, secrets, and private account paths stay out of scope.
Protect sign-up and login
Monitor account creation, login, upgrade, or billing paths that support teams hear about first when they fail.
Sell outcome-focused monitoring
Offer client boards that show whether the business journey works, not only whether the homepage is online.
Transaction flows are reserved for higher-value boards.
Start with public uptime, content, SSL, DNS, and status checks. Add transaction-flow capacity when a journey is important enough to justify heavier runtime.