MageSentinel on a Magento store: a walkthrough of the dashboard
This is what monitoring a Magento checkout with MageSentinel looks like day to day — from adding the store to the alert that arrives when a deploy breaks shipping. The screens below use demo data.
Adding the store
You add a store with its URL and a test product. There is nothing to install: MageSentinel works from outside, in a real browser, and finds its way through Luma, Hyvä Checkout or a one-step checkout on its own.
You choose how often it runs — every 30 minutes on Solo and Starter, every 15 on Agency, every 5 on Scale — and where alerts go: Slack, email or a webhook. An optional read-only Magento module adds root-cause data such as installed modules and recent errors, but monitoring never depends on it.
What a run checks
Each run walks the purchase: product page, add to cart, cart, checkout, address, shipping, payment, and — only if you enable it — placing a real order. At each step it checks the result, not just the page: the SKU and price in the cart, the shipping methods, the totals and their arithmetic, a payment method ready to accept input.
When a step fails, the run keeps the evidence: a screenshot of that step, a browser trace, a network log and the console errors, with secrets removed at capture time. The failure gets a stable code such as SHIPPING_NO_METHODS, so you know which part of the store to look at before opening anything. It is exactly the case described in five ways a Magento deploy breaks checkout.
The overview
The overview answers one question at the top: can every store take orders right now? Below it, a funnel shows how the latest runs did at each step across all stores, with checkout success rate, median and slow-tail duration, and failed checks.
Runs that could not reach a conclusion — a Cloudflare challenge, a maintenance page — are marked UNKNOWN and never page anyone. That keeps alerts rare enough to trust, the point of avoiding alert fatigue.
Incidents and alerts
Repeated failures with the same code on the same store become one incident, not fifty alerts. You get one alert when the store goes from PASS to FAIL, and one when it recovers; a cooldown stops repeats in between. Each incident is classified by impact — all customers, some, none or unknown.
After a fix, “Run now” checks the store immediately, so you can confirm the checkout works without waiting for the next scheduled run. Alongside, HTTP uptime monitors check every minute on paid plans — useful, but as uptime alone misses broken checkouts, they complement the purchase check rather than replace it.
Try it on your store
Every plan starts with a 14-day free trial, no card required. Add one store, pick a test product, and the first run completes within minutes.
Check your own store now with the free Magento checkout test: it walks the checkout in a real browser, Luma or Hyvä, and shows the step where it stops.
Find out your checkout broke before your customers do.
Real checkout checks for Magento and WooCommerce · 14 days free · no card requiredCommon questions
How do I add a Magento store to MageSentinel?
Enter the store URL; MageSentinel finds a product and runs the checkout. The optional connector module adds server diagnostics and real order placement.
Does MageSentinel place real orders on Magento?
Only when the store has its own connector token installed; the module can also cancel those test orders automatically.
Which Magento checkouts does it support?
Luma, Hyvä Checkout and common one step checkout extensions.