How is this different from an uptime monitoring service?

An external uptime service checks that the home page answers. This module sees what happens inside the shop: PHP errors on the checkout page, refused payments, customers who reach the payment step without ordering, a drop in sales. It also includes an uptime check, and it can call an external heartbeat to cover a complete server outage, which the module cannot report by itself.

Do I need a cron task?

It is recommended, every 5 minutes, from the command line or through a token-protected URL called from your hosting panel or an external cron service. Without a cron, and with PHP-FPM, the checks are triggered by visitor traffic, at most every 10 minutes and after the page has been sent. Fatal errors and failed payments are reported in real time in every case.

Does the module slow the shop down?

Errors are kept in memory during the request and written at the end. Response time tracking adds one database write per measured page, and the share of measured pages can be set from 1 to 100% for high-traffic shops. Checks and notifications run after the response has been sent to the visitor.

Do notifications contain customer data?

No. Page addresses are stored without their parameters, the call stack is stored without function arguments, and the server path and admin folder name are removed before anything is sent. Telegram tokens and webhook addresses are masked in the notification log.

How does acknowledging from a phone work?

Each alert notification contains a signed link. It opens a confirmation page on your shop, and the alert is acknowledged only when you confirm. Mail security scanners that open links automatically therefore cannot acknowledge it for you. After acknowledgement, reminders stop but you are still told when the problem is resolved.

Are there errors the module cannot see?

A fatal error raised before modules are loaded, for example in a configuration file, is not caught by the error handler; the uptime check and the 5xx error rate still report it. Checkout conversion detection relies on the display hook of the payment step, which some third-party one-page checkout modules do not call: in that case the order drop check still applies.

PrestaShop Monitoring & Downtime Alerts Module 8 & 9

PrestaShop Monitoring & Alerts: Downtime, PHP Errors, Failed Payments

Your shop tells you when something is wrong, before your customers do.

A module update that breaks the checkout on a Friday night, a payment gateway that has refused every card for two hours, an SSL certificate that expires during the holidays: without an on-call agency, these outages are found on Monday, in customer emails. This module watches the shop around the clock and sends a precise alert as soon as a problem appears, naming the module most likely at fault, then a message when everything is back to normal.

At a glance

PHP fatal error reported within seconds, with the module or theme most likely responsible
Failed payments, checkout conversion collapse and order drops compared with your usual activity
Uptime check every 5 minutes, response time measured on real visits
Alerts by email, Telegram, Slack, Discord or webhook, acknowledged in one click from a phone
SSL certificate, disk space and cron task monitored, weekly email report

PrestaShop 8 & 9 Email, Telegram, Slack, Discord Error origin Multistore

30-day refund

12 months updates

24h support

The long version

Everything you'd want to know before you install.

A detailed look at how PrestaShop Monitoring & Alerts: Downtime, PHP Errors, Failed Payments works, why we built it the way we did, and the thinking behind the features above.

§ 01

Built for merchants without an on-call agency

Some agencies watch their clients' shops, but most merchants have nobody reading the logs at 11 pm. The module does that job: it watches the shop continuously, keeps its alerts for real problems and sends them to the channel you already check. The dashboard sums up the state of the shop in one sentence, then details availability, response time, errors, payments and orders.

§ 02

PHP errors you can get fixed

A blank page does not say who caused it. The module records each error with its file, line, page, number of occurrences and probable origin. Identical errors are grouped, a new fatal error triggers an alert within seconds, and the copyable report gives the developer of the module concerned everything needed to reproduce the problem. Server paths and the admin folder name are masked before anything is sent.

§ 03

A shop that answers but no longer sells

Classic uptime tools do not see a broken payment gateway. The module records every cart that reaches the payment step, compares it with the orders created, then with the usual rate of the shop over 28 days. It also tracks orders moved to a failed payment status, with a breakdown by module, and the drop in orders against the same time slot of the previous four weeks. Thresholds take your volume into account: a small shop on a Sunday night does not get an alert.

§ 04

Alerts that do not flood you

A problem opens a single alert, updated while it lasts. Reminders are spaced according to your setting and stop as soon as you acknowledge, from the back office or from the link in the notification. A message tells you when the problem is resolved. An hourly cap protects your inbox if everything breaks at once, quiet hours let only critical alerts through, and the pause suspends notifications during an update without stopping detection.

§ 05

The silent causes of outages

Some outages give days of warning. The module reads the SSL certificate served by your domain every 6 hours and warns you before it expires, watches free disk space and reports when the cron task stops. To cover the case where the whole server goes down, an external heartbeat URL (Healthchecks.io, Better Stack) can be called at every cron run.

PrestaShop Monitoring & Alerts: Downtime, PHP Errors, Failed Payments

The short version.

The faulty module named in the alert

Sales are monitored, not just the server

Alerted where you already are

No false alarm on a Sunday night

Everything you'd want to know before you install.