| 开发者 | platkadigital |
|---|---|
| 更新时间 | 2026年9月8日 11:56 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | MIT |
| 版权网址: | 版权信息 |
SAVEQUERIES
is enabled) each $wpdb query as its own span. Detectors flag N+1 queries, slow endpoints, slow queries,
SELECT *, query floods and unhandled exceptions in the traces this plugin sends.
Setup is one button. Open MetrixWire → Connect and click Start monitoring: the plugin creates your
MetrixWire workspace, its project and its API key for you. No email address, no password, no URL to enter —
add an email and password later, under Account, whenever you want to sign in on the web too.
From then on everything lives in wp-admin:
SAVEQUERIES status.SAVEQUERIES is enabled — the SQL text and duration of each database query. The admin screens read this
site's own monitoring data back from the same service. Nothing is sent before you connect, and nothing is
sent while the "Send traces from this site" toggle is off. Traces leave the site on the shutdown hook,
after the response has already reached the visitor.
Service terms: https://metrixwire.com/terms — Privacy policy: https://metrixwire.com/privacy
metrixwire-apm folder to /wp-content/plugins/.define( 'SAVEQUERIES', true ); to wp-config.php to capture per-query spans.No — and you don't need to create one by hand either. One click on the connect screen sets everything up. The account has no email or password until you add them under Account, which you only need if you want to sign in on metrixwire.com directly or recover the account later. If you already have an account, use Sign in instead on the connect screen.
Nowhere. The plugin uses the hosted service at metrixwire.com. If you run MetrixWire yourself, point the
plugin at it with define( 'METRIXWIRE_ENDPOINT', 'https://your-instance.example.com' ); in
wp-config.php.
No. Connecting, reading issues, changing settings, managing alert rules and checking plan usage all happen in wp-admin. The Open MetrixWire button is there when you want the full dashboard, and signs you in automatically. Changing your paid plan is the one thing that leaves WordPress, because checkout is handled by the payment provider.
Yes. Define METRIXWIRE_KEY, METRIXWIRE_ENDPOINT, and optionally METRIXWIRE_ENABLED as constants in
wp-config.php — they take precedence over the saved settings, and the fields they cover are shown
read-only. A site configured this way traces without connecting, though the in-dashboard screens still
need a connection, since reading data back takes its own credential.
SAVEQUERIES must be defined as a constant in wp-config.php; WordPress reads it before any plugin loads,
so it can't be turned on from a settings screen at runtime.
Traces are sent on the shutdown hook, after the response has already been sent to the visitor, over a
short-timeout non-blocking request. Failures to reach MetrixWire are swallowed silently. The admin screens
cache what they read for a minute, so browsing them doesn't hammer the service either.
Anyone who can administer this WordPress site — the screens require the manage_options capability, and
the Open MetrixWire button signs that administrator into the connected account.
Yes. Each site connects separately, keeping its own project and credentials, and uninstalling removes those from every site in the network.
The site stops tracing and its credentials are removed. Your MetrixWire project and its history are kept, so signing back in later picks that project up instead of starting a new one.
wp-config.php constants alone no longer posts its traces where nothing is
listening. Sites that set METRIXWIRE_ENDPOINT themselves are unaffected.METRIXWIRE_ENDPOINT in wp-config.php.metrixwire-apm, with translation-ready strings and a
bundled .pot template.metrixwire_apm_*; activation migrates values saved by the 1.0 plugin.wp_remote_post() instead of cURL, so the site's HTTP transport, proxy
settings and filters apply.METRIXWIRE_ENDPOINT in wp-config.php.metrixwire-apm, with translation-ready strings and a
bundled .pot template.metrixwire_apm_*; activation migrates values saved by the 1.0 plugin.wp_remote_post() instead of cURL, so the site's HTTP transport, proxy
settings and filters apply.