Features · Investigate problems
See what changed before payments stopped.
Operanse records the plugin, setting and product changes that tend to explain an incident, and puts them beside it, so the first question after something breaks has an answer to start from.
On Monitor and Insight
- 09:12ChangeStripe settings: testmode, enabledadministrator · wp-admin
- 09:31ObservedPayments failing: 7 of the last 9 first attemptsusual for this hour: 0–1
- 10:02IncidentPayments failing, critical. Alert sent.changes just before it: 1
After something breaks, the first question is what changed
Payments stop on a Tuesday morning. Somebody updated a plugin, somebody else saved the gateway settings, and the host applied an update overnight. Nobody remembers the order, and wp-admin does not keep one.
- A problem with no error page and no obvious cause.
- Several people, or an agency, with access to wp-admin.
- Time spent reconstructing the morning instead of fixing it.
What you can see
Find the relevant change
Four kinds of change are recorded the moment they are saved: software, settings on the money path, products and privileged roles. Each is stated in a line you can read, with the versions either side of an update.
| kind | example | status |
|---|---|---|
| Software | WooCommerce Stripe Gateway 9.4.1 → 9.5.0 | updated |
| Settings | Shipping zone settings: methods | saved |
| Products | Annual box: price, sale dates | changed |
| Roles | A user given administrator | granted |
Put it beside the incident
An incident lists the changes that came just before it, with when and how each was made: in wp-admin, over the REST API, from WP-CLI or from cron.
On Insight, the AI review can cite a change as evidence, labelled as a lead to check, not a cause.
- observed
- 7 of 9 first attempts failed since 09:31
- usual
- 0–1 failures for Tuesday 09:00–10:00
- change before it
- 09:12 · Stripe settings: testmode, enabled · administrator, wp-admin
Keep secret setting values out of telemetry
A gateway’s settings hold its secret keys. So a settings change is recorded by name and by which keys changed, never by what they were or became. Stock quantities are not recorded at all: integrations write them on every order.
- what
- Stripe settings saved
- keys changed
- testmode, enabled
- values
- not recorded
- by
- an administrator, in wp-admin
- when
- Tue 09:12:40
The Changes tab, the incident, and Playback
The same record appears in three places, so nobody has to look it up twice.
- 07:55SoftwareWordPress 6.8.2 → 6.8.3cron · automatic update
- 08:40ProductStarter kit: publishedshop manager · wp-admin
- 09:12SettingsStripe settings: testmode, enabledadministrator · wp-admin
- 11:20SoftwareWP Mail SMTP 4.4 activatedadministrator · WP-CLI
In Playback each change is a marker on the day, so the update at 09:12 sits exactly where it happened against orders and payments.
The rows above are illustrative. Operanse records the role, the source and the WordPress user ID number; never a login, name or email address.
Coverage and limits
What it covers
- Software. Plugin, theme, WordPress and WooCommerce updates, activations and switches, with the versions either side.Monitor
- Settings on the money path. Payment, shipping, tax, checkout page, permalink, cache and SMTP settings, by name and changed key. Never a value.Monitor
- Products. A product published or unpublished, its price or sale dates changed, or its stock status changed.Monitor
- Roles. A user given or losing a privileged role, with the role and source of whoever changed it.Monitor
Limits
- Not an activity log of everything in wp-admin. Posts, comments, logins and options outside the recorded list are not recorded.
- A change just before a problem is a lead to investigate, not proof that it caused it.
- A change carries a role, a source and a user ID number, never a login, name or email address.
- It records a change; it cannot undo one. It is read-only.
View every recorded change
- Software. A plugin activated, deactivated or updated, a theme switched, WordPress or WooCommerce updated, with the versions either side.
- Settings on the money path. WooCommerce settings, each payment gateway’s settings, shipping and tax, the cart, checkout and shop page assignments, permalinks, the site address and time zone, the caching plugin’s settings and the SMTP plugin’s settings. A setting is recorded by name, with which of its keys changed.
- Products. A product or variation published or unpublished, its price or sale dates changed, or its stock status changed.
- Roles. A user given or losing a privileged role, such as administrator.
- How. Each change carries the role of the person who made it and the source: wp-admin, the REST API, WP-CLI or cron.
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
- Changes are recorded from pairing on. Nothing to configure; earlier changes are not backfilled.
Monitor On Monitor and Insight. Compare plans
Questions
Is this an activity log?
No. It records the changes that tend to explain a store incident: software, money-path settings, products and privileged roles. A full activity log of logins, posts and comments is a different tool.
Does it record who made the change?
It records the role (administrator, shop manager), the source (wp-admin, REST API, WP-CLI, cron) and the WordPress user ID number. It never records a login, display name or email address.
Does it store my gateway keys or settings values?
No. A settings change is recorded by the setting’s name and which keys changed. The values are never read into telemetry.
Can it roll a change back?
No. Operanse is read-only by construction: it has no code path that can change the site.