Will the plugin slow the store down?

No. None of its code runs on a customer request and nothing reaches the storefront. The checks are made by our servers, from outside.

Do I need a PingView account first?

No. In the plugin panel you give an email address and consent, and the account, team, monitor and API key are created for you. If you already have an account, you paste a write-scoped key.

The plugin is free, and the free plan is enough to watch a store. Paid plans add locations, deep scans and synthetic purchase paths.

What happens if I deactivate the plugin?

The monitor keeps running on our side and the alerts still arrive. You only lose the panel inside the store admin.

Does this replace a security or caching plugin?

No. It is an external check of what the store sends over HTTP. It caches nothing, minifies nothing, and it is neither a firewall nor a malware scanner.

Magento 2, Adobe Commerce and Mage-OS module

A thin module in the admin, all the work on our side

One Composer command and the admin carries uptime, response time, certificate, security headers and Core Web Vitals. The module declares not a single cron job and runs no code on customer requests: the probes run with us.

Install the plugin See what is in the panel

Free, no card
No cron, no storefront code
Four commands and you are done

version 1.2.0 · requires Magento Open Source / Adobe Commerce 2.4.4+, Mage-OS 3.x · PHP 8.1 – 8.4

your-store.com/admin

PingView

your-store.com

Operational

Status

Operational

Uptime, 24h

99.98%

Response time

284 ms

Needs attention

All clear

Availability

24h agonow

Last 24 hours: 99.98%
Last 7 days: 99.91%

Checked from 5 locations

PLWrocław118 ms
DEFrankfurt173 ms
GBWorcester140 ms
USNewark248 ms
ITMilan296 ms

The SSL certificate expires in 26 days. Renew it before the browser starts warning your customers.

The plugin panel inside your store's own admin. Location and card names are real; the numbers are illustrative.

Three nights the store was not selling

This is not about charts. It is about who tells you, and how long that takes.

3:40 in the morning, the host restarts the database: Without monitoringThe store answers 500 for forty minutes. You find out in the morning, from a customer who could not pay.; With the PingView pluginAn alert after the second failed check, by email and on the channel your team watches anyway.
Tuesday, the SSL certificate expires: Without monitoringThe browser shows a scary warning. Traffic is there, carts are not, and the cause looks like a bad campaign.; With the PingView pluginThe panel counts down the days to expiry and reminds you thirty days ahead. Same for the domain.
Friday, a new theme goes live: Without monitoringOn your desk everything flies. On a customer's phone the checkout takes eight seconds and half the carts stay empty.; With the PingView pluginLighthouse and Core Web Vitals measured from outside after changes, and a performance drop over twenty percent is an alert.

Six questions the panel answers without a single click

The plugin computes nothing on its own. It renders what the PingView backend computed, in the place you happen to be.

Is the store up right now?: One word in the header: operational, degraded, partial, offline or maintenance. Exactly the state your team sees in PingView and your customer sees on the status page.
Is it my store or my connection?: The result from every probe separately: Wroclaw, Frankfurt, Worcester, Newark, Milan. Four see the store and one does not, so this is not a store outage.
How long was the store down this week?: Uptime for 24 hours and for 7 days, plus an hour-by-hour chart. No spreadsheet arithmetic, and no argument with the host about whether the outage happened at all.
Is the checkout actually taking orders?: A synthetic purchase path walks the cart and the checkout and asserts that the steps really happened. A homepage can answer 200 long after the payment step has died.
What should I fix first?: A list of things to do, most urgent first: an expiring certificate, a missing security header, a page that got slower. Sentences to tick off instead of a chart to interpret.
Who finds out while I am asleep?: Email works out of the box. Then you route incidents to the channel your team already watches: Slack, Microsoft Teams, Discord, a webhook or SMS.

A cron monitor that does not depend on cron

The module deliberately declares no cron job of its own. A pinger driven by Magento cron cannot report that Magento cron has stopped. Instead you add one line to the crontab that already runs bin/magento cron:run, and silence on our side is the alert.

The plugin computes nothing on your server

A store that is down cannot report that it is down. So the checks run from outside, and the plugin is only a window onto the result.

No code on customer requests

Not a line of the plugin runs when a customer opens a page. Nothing is added to the store's response time and nothing lands on the storefront.

Checks from five countries

The probes run on our servers in Poland, Germany, the United Kingdom, the United States and Italy. An outage at your host does not touch them.

Disconnecting does not stop the monitoring

Disconnecting removes the credentials stored in the store. The monitor keeps running, the history stays, the alerts still arrive.

Twenty cards every plugin has to render

This is a contract, not a feature list: a plugin build fails if one of these cards disappears from the panel. We also show the three places where one platform does less than the others.

Plugin panel cards and their availability on the three platforms
Panel card	WordPress	PrestaShop	Magento 2
Store state in one wordOperational, degraded, partial, offline or maintenance in the panel header.
Four numbers up frontStatus, 24h uptime, response time and what needs attention.
What to fixSentences to tick off, most urgent first, computed by the backend.
Uptime, 24h and 7 daysPercentages plus an hour-by-hour chart.
What exactly is checkedThe interval, the locations and the conditions that raise an alert.
Watched store addressesCart, checkout, a category and a product, discovered from your store.
Alert channelsEmail, Slack, Teams, Discord, webhook and SMS, with a link to the settings.
Each probe on its ownStatus and latency per location, so an outage is told apart from a bad link.
Certificate and domainDays to SSL and domain expiry, plus a plain-HTTP warning.
Security headersThe Mozilla Observatory grade and the headers you are missing.
Lighthouse and Core Web VitalsPerformance, accessibility, best practices and SEO, measured from outside.
Purchase pathA synthetic run through the cart and the checkout, with its assertions.			no verification state
Recent incidentsWhen they started, how long they lasted and how they ended.
Is the store's schedule aliveA diagnosis of the store's cron plus a heartbeat monitor on our side.		cron line on your hosting	cron line on your hosting
Status badgeA preview and a snippet to paste, next to the public status page.
Repoint after an address changeWhen the store changes domain, the monitor follows it.	automatic	one click	one click
Account and teamWhich PingView account this store reports into.
Monitoring outside the storeA plain statement that the checks do not run on your server.
Into the full productA link to the account with history, reports and status pages.
Disconnect the storeRemoves the local credentials; the monitor keeps running.

Install

The account is created along the way, inside the store admin. Nothing to sign up for first.

1
Install and enable the module with the commands beside this list. Composer puts it in vendor, so it survives a rebuild of the deployment artifact.
2
In production mode also run setup:di:compile and setup:static-content:deploy.
3
Open System, PingView Monitoring, enter an email address and press start. You can paste a write-scoped API key instead.
4
The panel fills in after the first check. Alternatively, download the ZIP package and unpack it into app/code.

store terminal

$ composer require pingview/module-monitoring$ bin/magento module:enable PingView_Monitoring$ bin/magento setup:upgrade$ bin/magento cache:flush

Before you install

Will the plugin slow the store down?: No. None of its code runs on a customer request and nothing reaches the storefront. The checks are made by our servers, from outside.
Do I need a PingView account first?: No. In the plugin panel you give an email address and consent, and the account, team, monitor and API key are created for you. If you already have an account, you paste a write-scoped key.
What does it cost?: The plugin is free, and the free plan is enough to watch a store. Paid plans add locations, deep scans and synthetic purchase paths.
What happens if I deactivate the plugin?: The monitor keeps running on our side and the alerts still arrive. You only lose the panel inside the store admin.
Does this replace a security or caching plugin?: No. It is an external check of what the store sends over HTTP. It caches nothing, minifies nothing, and it is neither a firewall nor a malware scanner.