If your site buffered events in a directory outside the web root that the plugin chose itself, they are moved at the next daily check. Set OPERANSE_DATA_DIR to keep a directory outside the web root.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3776250,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3776250,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3776250,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3776250,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.9.4"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3776250,"resolution":"1","location":"assets","locale":"","width":2028,"height":684},"screenshot-2.jpg":{"filename":"screenshot-2.jpg","revision":3776250,"resolution":"2","location":"assets","locale":"","width":1206,"height":1022},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3776250,"resolution":"3","location":"assets","locale":"","width":1206,"height":1366},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3776250,"resolution":"4","location":"assets","locale":"","width":1206,"height":802}},"screenshots":{"1":"Playback, on Monitor and Insight: a store's morning replayed against its own normal. A payment gateway update, failing payments, a warning, then a critical alert, and recovery after the rollback (example store, not real data).","2":"Learned monitoring, on Monitor and Insight: each metric is drawn against the store's normal for that hour of the week. Here, orders paid at Stripe but never completed leave the expected range (example store).","3":"An alert email on Monitor and Insight: what changed, the store's usual range, an estimate of the revenue affected, and what Operanse did not verify. Watch alerts arrive by email too, for its fixed checks (example store).","4":"Asking your own AI assistant about your store over Operanse's read-only connection, on Monitor and Insight (example store)."}},"plugin_section":[],"plugin_tags":[1110,5603,4079,29148,286],"plugin_category":[45,54],"plugin_contributors":[197300],"plugin_business_model":[],"class_list":["post-388814","plugin","type-plugin","status-publish","hentry","plugin_tags-alerts","plugin_tags-monitoring","plugin_tags-subscriptions","plugin_tags-uptime","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-security-and-spam-protection","plugin_contributors-jeswd","plugin_committers-jeswd"],"banners":{"banner":"https:\/\/ps.w.org\/operanse-agent\/assets\/banner-772x250.png?rev=3776250","banner_2x":"https:\/\/ps.w.org\/operanse-agent\/assets\/banner-1544x500.png?rev=3776250","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/operanse-agent\/assets\/icon-128x128.png?rev=3776250","icon_2x":"https:\/\/ps.w.org\/operanse-agent\/assets\/icon-256x256.png?rev=3776250","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/operanse-agent\/assets\/screenshot-1.png?rev=3776250","caption":"Playback, on Monitor and Insight: a store's morning replayed against its own normal. A payment gateway update, failing payments, a warning, then a critical alert, and recovery after the rollback (example store, not real data)."},{"src":"https:\/\/ps.w.org\/operanse-agent\/assets\/screenshot-2.jpg?rev=3776250","caption":"Learned monitoring, on Monitor and Insight: each metric is drawn against the store's normal for that hour of the week. Here, orders paid at Stripe but never completed leave the expected range (example store)."},{"src":"https:\/\/ps.w.org\/operanse-agent\/assets\/screenshot-3.png?rev=3776250","caption":"An alert email on Monitor and Insight: what changed, the store's usual range, an estimate of the revenue affected, and what Operanse did not verify. Watch alerts arrive by email too, for its fixed checks (example store)."},{"src":"https:\/\/ps.w.org\/operanse-agent\/assets\/screenshot-4.png?rev=3776250","caption":"Asking your own AI assistant about your store over Operanse's read-only connection, on Monitor and Insight (example store)."}],"raw_content":"\n
A WooCommerce store can look perfectly normal and still be losing money. The home page loads, but subscription renewals have been failing since a gateway update. Background tasks stalled overnight, so orders were never completed. Someone switched off the last payment method. Uptime checks don't see any of this, and you usually find out from a customer.<\/p>\n\n
Operanse watches the activity behind your store, such as orders, payments, renewals and background tasks, and emails you when something stops working.<\/p>\n\n
Operanse does not change your store's content, orders, products or settings. The plugin keeps only its own monitoring data on your site: its settings, two tables, scheduled events and a small buffer.<\/p>\n\n
Prices are in US dollars, per live store. Staging and development copies are free on the paid plans.<\/p>\n\n
In short, Watch catches a defined set of failures. Monitor notices unusual behaviour and helps you investigate it. Insight adds server context and does the first analysis for you. Annual billing, allowances and limits are on the pricing page<\/a>.<\/p>\n\n The full list of what is collected, why, and how long it is kept follows under \"External services\".<\/p>\n\n Operanse can ask the plugin questions, for example \"how many scheduled actions failed in the last hour?\" or \"what is the status of order 1234?\". Each request names one capability from a fixed, read-only list built into this plugin, such as This plugin connects to the Operanse API<\/strong> ( Nothing is sent before an administrator pairs the site<\/strong> from Settings \u2192 Operanse (or The plugin sends the same data on every plan.<\/p>\n\n Operanse also contacts your site:<\/strong> our servers request your home page and a status URL ( Data is processed under the Operanse Terms of Service<\/a> and Privacy Policy<\/a>. The providers that process it on our behalf are listed on the Sub-processors<\/a> page.<\/p>\n\n\nWhat it does on your site, in brief<\/h4>\n\n
\n
What Operanse can access remotely<\/h4>\n\n
get_action_scheduler_summary<\/code>, get_order_state<\/code> or get_recent_operational_errors<\/code>. The plugin checks the request's parameters before answering. Requests are signed with a key created when you pair. A request cannot carry code. The plugin has no capability that writes data, runs SQL, PHP or shell commands, or changes a setting. These requests are used on the paid plans to investigate incidents. Watch makes none.<\/p>\n\nHow it handles failure<\/h4>\n\n
\n
Limitations<\/h4>\n\n
\n
External services<\/h3>\n\n
https:\/\/api.operanse.com<\/code>), run by JES WEB PTY LTD, to monitor your store. The plugin does nothing without an Operanse account.<\/p>\n\nwp operanse pair<\/code>). Pairing sends a one-time pairing code, your site URL, and the plugin, WordPress and PHP versions.<\/p>\n\nWhat is sent after pairing, and why<\/h4>\n\n
\n
insufficient_funds<\/code>) so Operanse can tell an ordinary decline from a fault. It does not send Stripe's message, the customer or the card.<\/li>\n\/proc<\/code> and cgroup files, free disk space, database status counters and settings (SHOW GLOBAL STATUS<\/code> and SHOW GLOBAL VARIABLES<\/code>), PHP OpCache status, and the PHP-FPM pool's worker counts.<\/li>\nwp-config.php<\/code> or .env<\/code> files. For each page a form is on, it sends the page's id, title and address (for example \"Checkout\" and \/checkout\/<\/code>), which any visitor can already see.<\/li>\nHow long it is kept, and how it is used<\/h4>\n\n
\n
\/?wc-api=operanse-probe<\/code>, which answers only when the site is paired) to check uptime. If you choose the optional direct-inbound connection mode, Operanse sends signed requests to the REST route operanse\/v1\/read<\/code>. By default the plugin polls for requests instead, and no inbound route is used.<\/p>\n\nBasic setup, about five minutes<\/h4>\n\n