Features · Keep operations running
Know when the services your store depends on stop answering.
Shipping rates, tax, CRM and ERP calls fail while every page loads fine. Operanse counts each service the site calls, failures and response times, names the plugin making the calls, and tells you when WooCommerce switches a webhook off.
On every plan, Watch (free) includedWatch: webhooks switched off. Monitor: the services the store calls, against their own normal.
| service | called by | failed | status |
|---|---|---|---|
| api.shipper.example | acme-shipping-rates | 86 of 94 | failing |
| api.stripe.com | woocommerce-gateway-stripe | 0 of 212 | ok |
| crm.example.net | acme-crm-sync | 2 of 31 | ok |
The site is up. The integration is not.
A shipping provider’s API starts answering 503. Checkout still loads, but rates fail and customers abandon. Elsewhere, an order webhook to your fulfilment system fails seven times in a row and WooCommerce quietly switches it off; from then on nothing is sent, so nothing fails, and every error count looks calm.
- Shipping rates or tax missing at checkout, with no error page.
- Orders not reaching the warehouse, ERP or automation tool.
- A webhook marked “disabled” that nobody disabled.
What you can see
Every service, and the plugin calling it
Each call the site makes through WordPress is counted by host: calls, failures (connection errors and 5xx answers), client errors kept apart, and the slowest answer. Since agent 0.9.7 each is tied to the plugin, theme or core code that made it.
Only the host leaves the site, never the path, query, headers or body.
- host
- api.shipper.example
- called by
- acme-shipping-rates
- calls · failed
- 94 · 86 (5xx)
- slowest answer
- 8.2 s
- path, query, body
- not recorded
Failures against the store’s own normal
Some integrations fail now and then, and that is normal for them. Operanse learns how often this store’s calls usually fail at each hour of the week, and alerts on an hour that is unusual, not on every timeout.
not priced: orders were unaffected
Webhooks WooCommerce switched off
WooCommerce disables a webhook by itself after repeated failed deliveries. Operanse alerts on exactly that decision: critical for order and subscription topics, a warning for products, customers and coupons. A webhook a person paused is shown as a change and never alerted.
| topic | delivers to | failures in a row | status |
|---|---|---|---|
| order.created | hooks.fulfil.example | 7 | off |
| product.updated | erp.example.net | 0 | active |
| customer.created (by a person) | crm.example.net | 0 | paused |
Two kinds of alert, kept apart
Examples. A failing service and a switched-off webhook are different problems with different owners.
- observed
- 86 failed calls this hour, usual 0–2
- called by
- acme-shipping-rates
- orders
- within the usual range: not priced
- by
- WooCommerce, after 7 failed deliveries in a row
- since then
- no order deliveries attempted
Coverage and limits
What it covers
- Outbound calls by service. Calls, failures and response times for each service the site calls through WordPress, and the plugin making them.Monitor
- Webhooks switched off. A WooCommerce webhook disabled after repeated delivery failures; critical when it carries orders or subscriptions.All plans
- Webhooks switched off are checked on every plan, Watch included: the check needs no learned normal.
- Your own integrations. Calls made through a vendor SDK or raw cURL can be reported with a WordPress action and are then counted like the rest. The six actions
Limits
- It sees calls made from PHP through the WordPress HTTP API. Calls from the visitor’s browser, raw cURL or processes outside WordPress are invisible unless your code reports them.
- A page served from cache makes no call, so a quiet service may simply be a cached site.
- It does not see whether a webhook’s receiver processed what it got, only whether WooCommerce switched the webhook off.
- It does not retry a call or re-enable a webhook. It is read-only.
Start using it
- Install the plugin from wordpress.org. It is read-only: it cannot change the site.
- Pair the site with the token from your dashboard. Setup, step by step
- Services appear as they are called. Webhooks are read on the next collection pass, within about ten minutes.
All plans On every plan, Watch (free) included. Watch: webhooks switched off. Monitor: the services the store calls, against their own normal. Compare plans
Questions
Which services does it watch?
Every host the site calls through WordPress: payment gateways, shipping, tax, CRM, ERP, marketing tools. Nothing to list in advance.
Does it record the URL or what was sent?
No. Only the host leaves the site. The path, query string, headers, request and response bodies and error messages stay on the server; an error is reduced to a class such as timeout or connection refused.
Why was the webhook not alerted when I paused it?
Only WooCommerce’s own decision to switch a webhook off after failed deliveries is alerted. A webhook a person paused or disabled is shown on the site’s timeline as a change.
Which plan includes it?
Outside services are on Monitor and Insight. Switched-off webhooks are alerted on every plan.