Stop Losing Revenue to Silent Failures.
Pulsar monitors your online store 24/7 — uptime, page checks, and smart alerting for any commerce platform. Install the optional Magento extension to unlock health collectors, checkout flow testing, and deep store insights.
P
Pulsar
Overview
Sites
Alerts
4
Settings
Guard Plan
Sites
8/10
Browser
1/2
Dashboard
Sites Monitored
8
Sites Up
8
Sites Down
0
Alerts Today
2
Recent Alerts
View All
WARN
Spark Fashion
Response time > 2000ms
INFO
Nordic Outdoors
SSL cert expires in 14 days
INFO
Acme Store
Health: cron (degraded)
Sites Status
Manage Sites
Acme Store
acme-store.com
Nordic Outdoors
nordic-outdoors.com
Spark Fashion
sparkfashion.co
+3 more sites
Recent Activity
Acme Store
UP
245ms
just now
Nordic Outdoors
UP
189ms
just now
Spark Fashion
UP
312ms
just now
Demo Wholesale
UP
156ms
just now
What is Magento monitoring?
Magento monitoring is the practice of continuously checking that a Magento store is not just online but actually working for shoppers — that category pages have products, search returns results, checkout completes, and background jobs (cron, indexers, queues) are keeping up. The hard part is that most Magento failures still return HTTP 200, so a generic uptime monitor reports the store as healthy while customers can't buy.
Pulsar covers this in two layers. From outside, global probes run sub-minute HTTP checks and a real Chromium browser walks the full Product → Cart → Checkout flow (with Luma and Hyvä presets) to catch front-end and payment regressions. From inside, an optional read-only Magento extension exposes 23 health collectors — indexer drift, cron heartbeat, queue backlog, OpenSearch cluster state, Redis evictions, PHP-FPM saturation, stuck pending_payment orders, SSL expiry, admin 2FA gaps, and more — surfacing internal state nothing external can see. Alerts route to Slack, Discord, email, or PagerDuty with per-collector noise controls.
HTTP 200 is the most expensive false positive in commerce
Generic uptime tools watch status codes. Pulsar watches whether customers can actually buy — and maps every failure mode to a specific Magento collector or browser signal.
Silent-Failure Detection
Most outages return HTTP 200. Empty categories from a drifted indexer, cron processes that died at 3 a.m., add-to-cart buttons broken by a JS error, zero-result searches from a red OpenSearch cluster — Pulsar maps each scenario to a specific collector and flags it the moment it starts. The thing Pingdom and Uptime Robot can't see is the thing Pulsar is built to catch.
External Synthetic Uptime
Sub-minute HTTP checks from global probes — works with any commerce platform, runs from outside your firewall so we don't go dark when your server does. Response times, status codes, SSL expiry, content substring matching, configurable redirects, and per-site basic-auth + custom headers. Browser-based checks load the page in real Chromium and capture `console.error` and unhandled exceptions before customers see them.
Checkout Flow Testing — Luma & Hyvä Presets
A real Chromium browser walks Product → Add to Cart → Cart → Shipping → Payment, every 5 or 15 minutes depending on your plan. Selectors ship preconfigured for Luma and Hyvä; custom themes drop in their own CSS selectors via the dashboard. Each step is timed independently — when a deploy breaks payment, the alert names the exact step and the JS error caught during the run.
23 Magento Health Collectors — in three sets
The optional `byte8/module-pulsar` extension exposes `/pulsar/health` with 23 collectors. The 14 platform collectors — cron heartbeat, indexer drift, queue backlog, OpenSearch cluster state, Redis memory + evictions, PHP-FPM saturation, disk, deploy state, SSL expiry, log errors — ship on every plan including Free. Guard adds the commerce set (stuck `pending_payment` orders, silently unsent order emails, broken integrations) and the security set (admin 2FA gaps, config hygiene, skimmer scanning in CMS content, web-shells in pub/media, exposed upload endpoints, applied-patch verification). Each collector has a per-site mute and a Critical-only override.
Security Advisories, Matched to Your Patched Reality
Pulsar ingests NVD, GitHub, Adobe and Sansec advisories and matches each one against the Magento version your store actually reports. The applied-patches collector verifies the fix is present in live code, so a CVE you've already patched is marked mitigated instead of paging you — and if a `composer install` quietly drops the patch, you get a regression alert. Guard and Fortress.
DNS, Third-Party Dependencies & Consent Guard
Three checks that live outside your server. DNS monitoring resolves your domain from an independent resolver and alerts on record changes or a DNSBL listing. Dependency checks assert that the payment SDK, consent CDN and tag scripts your checkout loads are still serving real content, not an empty file. Consent guard opens the storefront in a fresh browser and flags tracking that fires before a consent decision exists — the CMP fail-open your legal team never finds. Guard and Fortress.
Alert Routing With Real Noise Controls
Route alerts to Slack, Discord, email, or PagerDuty (Fortress). Each collector has individual override modes — Off, Critical only, or normal — so a flapping cron consumer can't drown the channel. Confirmation thresholds make sites alert only after N consecutive failures; site-level mute handles maintenance windows; auto-resolve fires when the run goes green again.
Supercharge with the Magento extension
Optional — uptime monitoring works out of the box for any store. The extension adds the 14 platform health collectors on every plan (Free included); Guard unlocks the commerce and security sets, checkout flows and advisories.
The Magento extension surfaces internal state nothing external can see
Each collector has an admin toggle, a per-site override (Off / Critical-only / normal), and a documented threshold. The 14 platform collectors run on every plan — including Free, at a 15-minute poll. The commerce and security sets are Guard and Fortress. The extension source is published on GitHub for review.
Pipeline & async
Every plan, including Free
Where indexes and queues silently fall behind.
Cron
heartbeat, stuck jobs, queue depth
Indexer
invalid + stuck reindex states
Queue
MySQL + AMQP, pending + error counts
Log Errors
exception.log spike detection
Log
log file sizes, debug flag, error reports
Search & cache
Every plan, including Free
Where the catalog quietly stops being browsable.
Search
OpenSearch / Elasticsearch cluster health
Cache
type status + Varnish reachability
Redis
memory %, evicted keys, per-instance
Database
connectivity, threads, response time
Database Size
growth + table-level tracking
Runtime
Every plan, including Free
Where infrastructure quietly saturates.
PHP-FPM
pool saturation vs pm.max_children
System
PHP + Magento version, disk, memory
Deploy
mode, maintenance, DI, static version
SSL
certificate expiry + issuer
Commerce signals
Guard and Fortress
Where the store is up but nobody can buy.
Orders
stuck pending_payment, 24h failure rate
Transactional Email
order / invoice emails silently unsent
Integrations
broken integrations + revoked OAuth
Security posture
Guard and Fortress
Where compromise + config drift hide in plain sight.
Admin Security
failed logins, 2FA gap, locked accounts
Config Hygiene
template hints, minify, signing, rewrites
Content Integrity
skimmers injected in CMS blocks + config
Media Integrity
pub/media .htaccess + webshell detection
Upload Endpoint
suspicious POSTs to file uploaders
Applied Patches
verifies security patches in live code
Pulsar vs New Relic, Datadog & Uptime Robot
These tools watch different layers of the stack. APM (New Relic, Datadog) watches server health; uptime monitors (Uptime Robot, Pingdom) watch whether the URL responds; Pulsar watches whether customers can actually buy. Most teams run one of the first two and still miss the Magento-specific failures below.
| Capability | PulsarMagento-aware monitoring | New Relic / DatadogInfra & APM | Uptime Robot / PingdomHTTP uptime |
|---|---|---|---|
What it actually watches | Can customers buy? | Server health & traces | Does the URL respond? |
Catches silent failures (HTTP 200 but broken) | Partial (exceptions only) | ||
Reads Magento internal state | 23 health collectors | ||
Real-browser checkout-flow testing | Luma & Hyvä presets | Scriptable add-on | |
External synthetic uptime from global probes | Add-on | ||
JavaScript error capture (console.error, exceptions) | Browser-RUM add-on | ||
Magento security, advisories & config drift | |||
Setup | URL + optional extension | Agent on every host | URL only |
Cost model | Flat monthly | Per-host, metered | Free / low-cost |
doesn't mean working
Time to first alert
Magento health collectors
Checkout-flow interval on Fortress
How it works
Add your store
Enter your store URL in the Pulsar dashboard. Works with Magento, Shopify, WooCommerce, BigCommerce — any platform.
Get monitoring instantly
1-minute uptime checks, SSL expiry and instant alerts start immediately — free, no card. No code changes required.
Unlock deep insights
Install the read-only extension to add the platform health collectors on Free, then upgrade to Guard for checkout flows, the commerce and security collectors, advisories, DNS, dependencies and consent guard.
Pulsar Pricing
Monthly pricing shown. Billed monthly or save with annual.
Free
Real-time uptime for one Magento store, with the platform health collectors — free forever, no card
1 HTTP site · 3 monitored pages per site · 1 alert channel · 1-min check interval · Collectors polled every 15 min · 7-day history · 14 platform health collectors (cron, indexers, queues, cache, search…) · Slack & Discord alerts
Sentry
/mo
10 HTTP sites
10 monitored pages per site
1 real-browser checkout flow
1-min check interval
30-min checkout interval
Collectors polled every 5 min
30-day history
14 platform health collectors (cron, indexers, queues, cache, search…)
Content & keyword validation
Slack & Discord alerts
Guard
/mo
25 HTTP sites
25 monitored pages per site
10 real-browser checkout flows
1-min check interval
15-min checkout interval
Collectors polled every 5 min
90-day history
All 23 Magento collectors — platform, commerce & security
Content & keyword validation
Version-matched security advisories + patch drift
Third-party dependency checks
Consent guard (CMP fail-open)
DNS record-change + DNSBL monitoring
Slack & Discord alerts
Fortress
/mo
100 HTTP sites
100 monitored pages per site
25 real-browser checkout flows
1-min check interval
5-min checkout interval
Collectors polled every 5 min
1-year history
All 23 Magento collectors — platform, commerce & security
Content & keyword validation
Version-matched security advisories + patch drift
Third-party dependency checks
Consent guard (CMP fail-open)
DNS record-change + DNSBL monitoring
Slack & Discord alerts
PagerDuty integration
Frequently asked questions
What's a “silent failure”?
Does Pulsar work with platforms other than Magento?
What Magento versions does the extension support?
I have a custom Magento theme — does checkout-flow monitoring still work?
How do I keep alert noise under control?
Does Pulsar pair with Orbit?
How is Pulsar different from New Relic, Datadog, or Uptime Robot?
Is there a free plan, and what's in it?
Can I self-host Pulsar?
Start monitoring your store in 60 seconds
Free forever for one store, no card. Or take the full Guard feature set for a 14-day trial — cancel before billing starts.