{"id":394995,"date":"2026-10-29T07:39:31","date_gmt":"2026-10-29T07:39:31","guid":{"rendered":"https:\/\/de.wordpress.org\/plugins\/servermetry-backup-monitoring\/"},"modified":"2026-10-29T07:39:17","modified_gmt":"2026-10-29T07:39:17","slug":"servermetry","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/servermetry\/","author":23540762,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.1.4","stable_tag":"0.1.4","tested":"7.1.4","requires":"6.0","requires_php":"7.4","requires_plugins":null,"header_name":"ServerMetry Backup Monitoring","header_author":"FloBa Media","header_description":"Reports UpdraftPlus backup starts and final results to ServerMetry.","assets_banners_color":"","last_updated":"2026-10-29 07:39:17","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/servermetry.com\/docs\/backups","header_author_uri":"https:\/\/floba-media.de","rating":0,"author_block_rating":0,"active_installs":10,"downloads":66,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"0.1.4":{"tag":"0.1.4","author":"flobamedia","date":"2026-10-29 07:39:17","revision":3772311}},"upgrade_notice":{"0.1.3":"<p>Existing settings and backup reporting remain compatible. Read the external-service and removal information before configuring ping URLs.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3772310,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3772310,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3772310,"resolution":false,"location":"assets","locale":false}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.4"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[151,5603,151816],"plugin_category":[54,59],"plugin_contributors":[274901],"plugin_business_model":[],"class_list":["post-394995","plugin","type-plugin","status-publish","hentry","plugin_tags-backup","plugin_tags-monitoring","plugin_tags-updraftplus","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_contributors-flobamedia","plugin_committers-flobamedia"],"banners":[],"icons":{"svg":"https:\/\/ps.w.org\/servermetry\/assets\/icon.svg?rev=3772310","icon":"https:\/\/ps.w.org\/servermetry\/assets\/icon.svg?rev=3772310","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>ServerMetry Backup Monitoring connects UpdraftPlus to <a href=\"https:\/\/servermetry.com\">ServerMetry<\/a>, the monitoring service operated by FloBa Media. ServerMetry is our own product and brand. This plugin is not affiliated with UpdraftPlus.<\/p>\n\n<p>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.<\/p>\n\n<h4>Requirements<\/h4>\n\n<ul>\n<li>WordPress 6.0 or later and PHP 7.4 or later.<\/li>\n<li>UpdraftPlus installed and active for backup events. You can save settings before activating UpdraftPlus.<\/li>\n<li>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.<\/li>\n<li>Outgoing HTTPS access to the configured ServerMetry API endpoint.<\/li>\n<\/ul>\n\n<h4>Features<\/h4>\n\n<ul>\n<li>Start, success, warning, final failure and cancellation reports.<\/li>\n<li>One shared ping URL or separate URLs for file and database backup jobs.<\/li>\n<li>Stable run IDs across UpdraftPlus resumptions; identical targets receive one report.<\/li>\n<li>Up to three WP-Cron retries after a failed final delivery.<\/li>\n<li>Configured file\/database intervals and next UTC timestamps reported at backup start for optional schedule suggestions.<\/li>\n<li>Native WordPress settings with hidden stored ping URLs and explicit removal controls.<\/li>\n<\/ul>\n\n<p>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.<\/p>\n\n<h3>External services<\/h3>\n\n<p>This plugin relies on ServerMetry, operated by FloBa Media, to store monitoring events, show backup history and send configured notifications.<\/p>\n\n<p>Nothing is sent by this plugin until an administrator saves a valid ping URL under Settings &gt; ServerMetry. Saving a URL enables reports to that endpoint. No separate telemetry, visitor tracking, remote scripts, fonts or images are loaded by this plugin.<\/p>\n\n<h4>Where and when data is sent<\/h4>\n\n<p>Reports are HTTPS POST requests to the configured job ping URL. For the hosted service this is https:\/\/api.servermetry.com\/api\/v1\/backup\/ping\/YOUR_SECRET_TOKEN. A Dev setup uses https:\/\/dev-api.servermetry.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.<\/p>\n\n<p>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.<\/p>\n\n<h4>Data sent<\/h4>\n\n<ul>\n<li>The secret ping token in the request URL, which authenticates the backup job.<\/li>\n<li>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.<\/li>\n<li>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.<\/li>\n<li>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.<\/li>\n<\/ul>\n\n<p>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.<\/p>\n\n<p>Service: https:\/\/servermetry.com\nDocumentation: https:\/\/servermetry.com\/docs\/backups\nTerms of use: https:\/\/servermetry.com\/terms\nPrivacy policy: https:\/\/www.floba-media.de\/datenschutz<\/p>\n\n<h4>Local storage and stopping reports<\/h4>\n\n<p>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.<\/p>\n\n<p>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.<\/p>\n\n<p>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.<\/p>\n\n<p>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.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install the ZIP through Plugins &gt; Add New &gt; Upload Plugin and activate ServerMetry Backup Monitoring.<\/li>\n<li>Install and activate UpdraftPlus if it is not installed already.<\/li>\n<li>In ServerMetry, create a backup plan and jobs for the schedules you want to monitor.<\/li>\n<li>Open Settings &gt; ServerMetry, or select Settings in the plugin list.<\/li>\n<li>Enter the complete job ping URL without \/start or another status suffix. Use a shared URL or separate file\/database URLs, then save.<\/li>\n<li>Run a real UpdraftPlus backup. Check its start, final result and duration in the ServerMetry job history.<\/li>\n<li>Configure schedule, timezone, grace period, runtime limit and notification rules in ServerMetry. Match them to the real UpdraftPlus schedule.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"do%20i%20need%20a%20general%20servermetry%20api%20key%3F\"><h3>Do I need a general ServerMetry API key?<\/h3><\/dt>\n<dd><p>No. The secret job ping URL authenticates these reports. Account access is required to set up the plan and jobs in ServerMetry.<\/p><\/dd>\n<dt id=\"are%20files%20and%20database%20measured%20separately%3F\"><h3>Are files and database measured separately?<\/h3><\/dt>\n<dd><p>Separate backup runs can report to separate jobs. A combined backup with two different targets sends the same overall start and result to both. This does not measure the internal file and database phases separately.<\/p><\/dd>\n<dt id=\"why%20is%20a%20runtime%20missing%20or%20longer%20than%20expected%3F\"><h3>Why is a runtime missing or longer than expected?<\/h3><\/dt>\n<dd><p>Runtime uses ServerMetry receipt times. A lost start is not replayed after completion and can leave the result without a duration. Network delays and final-result retries can increase the measured duration.<\/p><\/dd>\n<dt id=\"what%20happens%20if%20a%20backup%20process%20stops%20unexpectedly%3F\"><h3>What happens if a backup process stops unexpectedly?<\/h3><\/dt>\n<dd><p>A terminated PHP process cannot reliably send a final result. Configure overdue and runtime rules in ServerMetry. Temporary UpdraftPlus errors with a planned resumption do not count as final failures.<\/p><\/dd>\n<dt id=\"how%20do%20retries%20work%3F\"><h3>How do retries work?<\/h3><\/dt>\n<dd><p>Final results have at most four attempts: the first request and three WP-Cron retries after 1, 2 and 3 minutes respectively. Network errors, HTTP 408\/429\/5xx and unexpected responses can be retried. Other permanent 4xx errors are not retried. Each request has a three-second timeout.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20change%20my%20schedule%3F\"><h3>Does the plugin change my schedule?<\/h3><\/dt>\n<dd><p>No. At the next new backup start it reports configured intervals and next timestamps. In ServerMetry you can review, apply and save a schedule suggestion. Different file\/database schedules should use separate jobs. Fixed WP-Cron intervals can be delayed by site traffic and can shift in local time at daylight-saving changes. Premium and incremental schedules need separate verification.<\/p><\/dd>\n<dt id=\"does%20it%20support%20coolify%20or%20restores%3F\"><h3>Does it support Coolify or restores?<\/h3><\/dt>\n<dd><p>Not through this plugin. Configure Coolify's separate webhook integration in ServerMetry. Do not put a Coolify webhook URL in these fields. Restore, migration, backup size and backup integrity checks are outside this plugin's scope.<\/p><\/dd>\n<dt id=\"which%20languages%20are%20available%3F\"><h3>Which languages are available?<\/h3><\/dt>\n<dd><p>Settings currently use German source strings and the servermetry text domain. They are ready for community translation through WordPress.org. This package does not claim that English or other language packs are available.<\/p><\/dd>\n<dt id=\"what%20has%20been%20tested%3F\"><h3>What has been tested?<\/h3><\/dt>\n<dd><p>The isolated hook contract is checked against UpdraftPlus 1.26.13. It covers success, warning, cancellation, final failure and recovery after a temporary failure. These tests do not replace a complete WordPress installation and real backup test. Future UpdraftPlus terminal log-message changes require a new contract check. Multisite\/network activation and custom Premium schedules are not certified by these tests.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>0.1.4<\/h4>\n\n<ul>\n<li>Declare compatibility with WordPress 7.1, tested by the site owner on WordPress 7.1.3.<\/li>\n<li>Read upstream log translations from the UpdraftPlus catalogue without declaring them as ServerMetry interface strings. Preserve gettext filters.<\/li>\n<li>Use the servermetry text domain exclusively for interface translations.<\/li>\n<\/ul>\n\n<h4>0.1.3<\/h4>\n\n<ul>\n<li>Prepare WordPress.org directory metadata, service and data disclosure, installation instructions and FAQ.<\/li>\n<li>Make settings and delivery messages translatable without changing the backup report protocol.<\/li>\n<li>Explain the external service and activation of reports on the settings page.<\/li>\n<\/ul>\n\n<h4>0.1.2<\/h4>\n\n<ul>\n<li>Report configured UpdraftPlus schedules with backup starts for optional ServerMetry schedule suggestions. Different file and database schedules remain distinct.<\/li>\n<\/ul>\n\n<h4>0.1.1<\/h4>\n\n<ul>\n<li>Add Settings and Documentation links to the WordPress plugin list.<\/li>\n<li>Link configured Dev-only installations to the Dev dashboard.<\/li>\n<\/ul>\n\n<h4>0.1.0<\/h4>\n\n<ul>\n<li>Initial version for UpdraftPlus backup reports.<\/li>\n<\/ul>","raw_excerpt":"Report UpdraftPlus backup starts, results and schedules to ServerMetry. Monitor missed backups and runtime from one dashboard.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/394995","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=394995"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/flobamedia"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=394995"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=394995"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=394995"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=394995"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=394995"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=394995"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}