Documentation · Set up

Install and connect

Operanse is a WordPress plugin and a hosted service. The plugin observes your store and uploads what it sees on its own schedule. The dashboard at app.operanse.com is where you read it and where alerts are set up. Nothing is recorded until the two are connected.

Requirements

WordPress 6.4 or later and PHP 8.1 or later.
WooCommerce, for payments, orders, refunds and renewals. Forms, outgoing mail, outbound calls, errors, server resources and uptime are monitored on any WordPress site.
An Operanse account. New accounts start with 14 days of Insight, no card required, and move to the free Watch plan when the trial ends unless a payment method is added.

1. Install the plugin

In wp-admin, go to Plugins → Add New and search for Operanse, or install it from wordpress.org. With WP-CLI:

wp plugin install operanse-agent --activate

Activating the plugin records nothing and sends nothing. It waits to be paired.

2. Add the site in the dashboard

Sign in at app.operanse.com and add the site with its name and address. The site's time zone is read from WordPress when the plugin connects, so there is nothing to set by hand. A staging or development copy of a store is free on the paid plans; add it as its own site.

3. Pair the plugin

On the site's overview page in the dashboard, open Connect the plugin and create a pairing token. The token is shown once. In wp-admin, go to Settings → Operanse, paste it and press Pair. From the command line instead:

wp operanse pair <token>

Pairing gives the plugin its own credentials, and every request it makes from then on is signed with them. Nothing inbound is required: the plugin calls out on its own schedule, and the dashboard reads from our side.

What happens after pairing

Within a few minutes, Settings → Operanse shows Paired: yes and the dashboard shows the site as connected.
The first upload is an inventory: WordPress, PHP and database versions, plugins and themes with their versions, WooCommerce configuration (gateways by id, never credentials), scheduled tasks and REST routes. Later inventories are compared with it, which is what a recorded change on the dashboard means.
Uptime checks and the free plan's fixed checks start straight away.
Learned monitoring needs history. Most of a store's normal is ready after 48 hours of data; a store whose renewals run weekly needs two weeks. Fixed rules apply from day one, and the site page shows when each baseline will be ready.

Server setup: two lines in wp-config.php that keep the plugin's buffer private and its uploads on time. Recommended for every busy store.
Alerts: add the people and channels that should hear about an incident.
Team: invite the people who run the store.