About this plugin
ServerMetry Backup Monitoring connects UpdraftPlus to ServerMetry, the monitoring service operated by FloBa Media. ServerMetry is our own product and brand. This plugin is not affiliated with UpdraftPlus.
The plugin reports backup starts and final results. ServerMetry stores the history, calculates runtime from received events and can notify you about failures, warnings, missed backups and long runs. Configure monitoring and notification rules in ServerMetry.
Requirements
- WordPress 6.0 or later and PHP 7.4 or later.
- UpdraftPlus installed and active for backup events. You can save settings before activating UpdraftPlus.
- A ServerMetry account, a backup plan and at least one backup job. Service features and limits depend on your ServerMetry plan; paid plans are available. See https://servermetry.com/terms.
- Outgoing HTTPS access to the configured ServerMetry API endpoint.
Features
- Start, success, warning, final failure and cancellation reports.
- One shared ping URL or separate URLs for file and database backup jobs.
- Stable run IDs across UpdraftPlus resumptions; identical targets receive one report.
- Up to three WP-Cron retries after a failed final delivery.
- Configured file/database intervals and next UTC timestamps reported at backup start for optional schedule suggestions.
- Native WordPress settings with hidden stored ping URLs and explicit removal controls.
The plugin does not create backups, change UpdraftPlus schedules, modify UpdraftPlus email notifications or create ServerMetry alert rules. It does not check backup contents or verify that a backup can be restored.
External services
This plugin relies on ServerMetry, operated by FloBa Media, to store monitoring events, show backup history and send configured notifications.
Nothing is sent by this plugin until an administrator saves a valid ping URL under Settings > ServerMetry. Saving a URL enables reports to that endpoint. No separate telemetry, visitor tracking, remote scripts, fonts or images are loaded by this plugin.
Where and when data is sent
Reports are HTTPS POST requests to the configured job ping URL. com/api/v1/backup/ping/YOUR_SECRET_TOKEN. com instead.
Custom publicly reachable HTTPS hosts with the same API path are accepted; only configure an endpoint you trust. Redirects are disabled and WordPress validates outgoing URLs.
Requests occur when a configured UpdraftPlus backup starts or finishes and during limited retries of final results. Activating the plugin or opening its settings does not send a monitoring event.
Data sent
- The secret ping token in the request URL, which authenticates the backup job.
- Backup status, a run ID made from the WordPress site ID and UpdraftPlus backup nonce, and a short generic message. Completion messages can include the warning count.
- At backup start: the mapped components (files/database), their WP-Cron intervals in seconds and next scheduled UTC timestamps. Manual or absent schedules have empty interval/timestamp values.
- Standard HTTP connection metadata. The receiving server sees the sending server IP address and the WordPress HTTP user agent, which normally includes the WordPress version and site URL.
No backup files, database contents, original log lines, visitor data or WordPress login credentials are included in the report body. The ping token itself is a credential: do not publish it or include it in screenshots.
com
com/docs/backups
com/terms
de/datenschutz
Local storage and stopping reports
Ping URLs are stored in WordPress options without separate encryption and can be present in database backups. Only administrators with manage_options can change settings. Stored URLs are not returned in the form or exposed by this plugin through the REST API.
Empty fields keep existing values; use the removal checkbox and save to clear a URL.
Existing runs keep their initial URLs until completion or cleanup. Removing a setting stops new runs for that target, but not pending reports. Rotate the job ping URL in ServerMetry to revoke an old token immediately, or deactivate the plugin to stop its callbacks.
Run options are removed after delivery finishes or retry attempts are exhausted. A duplicate-suppression marker without the URL lasts one week. Stale run options are scheduled for cleanup after one week.
WP-Cron requires site traffic or an external cron trigger; cleanup and retries can be delayed.
Deactivation and deletion retain settings, last-delivery information and any pending run options/cron entries in WordPress. Cleanup cannot run while the plugin is absent. Reinstalling can resume pending reports.
Clear saved URLs, allow outstanding runs to finish and revoke tokens before permanent removal. Removing this plugin does not delete history in ServerMetry.