| 开发者 | fizteq |
|---|---|
| 更新时间 | 2026年4月9日 20:20 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp-pulse.app. No data is transmitted until you configure the plugin with your API key. The plugin does not contact any external server until you explicitly connect it.
Data transmitted to WPPulse:
[Filtered] before transmission. You can add custom fields on the settings page.
Service links:
WPPulse is operated by FizteQ Solutions SRL (Romania, EU). All data is processed and stored on servers located in Bucharest, Romania.
https://wp-pulse.app. No change needed unless directed otherwise.Yes. The plugin sends monitoring data to your WPPulse dashboard at wp-pulse.app. You can sign up for a free account to get started.
The plugin sends error details (message, file, stack trace), plugin change events, and environment information (PHP version, WordPress version, active theme). Sensitive fields like passwords, tokens, emails, and credit card numbers are automatically filtered and never transmitted.
No. The plugin hooks into WordPress events and only runs when something happens (an error, a plugin change, etc.). It adds no frontend JavaScript, no database tables, and no queries to page loads. API calls use a 10-second timeout so they never block your site.
Events are automatically queued locally (up to 50 events) and retried with exponential backoff. Once the connection is restored, all queued events are sent in a single batch. No data is lost.
Yes. Monitors are toggled from the WPPulse dashboard. After making changes there, click Sync Config in the plugin settings to pull the latest configuration.
Yes. Go to the WPPulse settings page and add field names under Additional Filtered Fields (one per line). These are merged with the 34 built-in filtered fields. You can also use the wppulse_sensitive_body_keys and wppulse_sensitive_header_keys filters in code.
WPPulse is built by an EU company (FizteQ Solutions SRL, Romania) and hosted entirely within the EU. Sensitive data is filtered before transmission, and the plugin does not use cookies or track visitors. See our privacy policy and DPA for full details.
The plugin detects WP-CLI and command-line contexts. Error monitoring works in CLI mode, but request-specific data (URL, headers, POST body) is not captured since there is no HTTP request.
Yes. The plugin reports the multisite status as part of the environment data. Install and configure it on each site in the network where you want monitoring.