
外掛標籤
開發者團隊
原文外掛簡介
When your site goes down or something breaks, SiteBeacon tells you by email, so you don’t hear it first from a customer.
SiteBeacon Reporter connects your WordPress site to SiteBeacon, a website monitoring service (uptime checks every 5 minutes, page content checks, SSL and domain expiry). The free plan monitors up to 2 sites, with no time limit.
Uptime checks from the outside can tell you that a site is down. They cannot tell you that a plugin update is waiting, that debug.log is filling up with fatal errors, or that someone changed a core file. This plugin reports those things from the inside.
Once an hour it sends a small JSON report to SiteBeacon:
WordPress, PHP and MySQL/MariaDB versions, and whether updates are available
Active theme and plugins with their versions, available updates and whether automatic updates are on (up to 200)
Inactive plugins with their versions and available updates (up to 50), and number of users per role (to notice a new administrator)
Number of fatal errors and warnings added to debug.log since the last report
Debug settings (WP_DEBUG, WP_DEBUG_DISPLAY, WP_DEBUG_LOG), the size of debug.log, and its path from the site URL when it is inside the WordPress folder (so SiteBeacon can check once a day whether it can be read from outside)
Last published post, next scheduled post, number of scheduled posts, and late WP-Cron events
Failed logins and lockouts in the last 24 hours (only when SiteGuard WP Plugin is used)
Once a day: the result of comparing core and plugin files with the checksums published by WordPress.org (counts, relative paths and the MD5 hashes of the reported files only)
The result of the last automatic update (counts and slugs only)
Whether minor WordPress core updates are installed automatically, what turns automatic updates off (AUTOMATIC_UPDATER_DISABLED, DISALLOW_FILE_MODS, or file changes not allowed), the last failed automatic core update (time, version and error code only), and whether WP-Cron is turned off (DISABLE_WP_CRON) or the next core update check is late
SiteBeacon shows these on the site’s page and emails you when something needs attention.
Nothing is sent until you save a token
Right after activation the plugin connects nowhere: not to SiteBeacon, and not to WordPress.org. Reports and the daily file check start only after you save a SiteBeacon token. When you remove the token, both stop.
What is never sent
User names, email addresses or display names
File contents, debug.log lines, error messages, or absolute server paths
Database name, table prefix, WP-Cron hook names, passwords, keys or tokens (the token is only used in the Authorization header)
Requirements
A SiteBeacon account. The free plan monitors up to 2 sites.
External services
This plugin connects to the following services. Nothing is sent, and no connection is made, until you save a SiteBeacon token.
SiteBeacon (s-m.biz) – the monitoring service this plugin reports to.
What is sent: the site host name (from the Home URL), the date and time of the report, the version of this plugin, WordPress version and available update, PHP version, MySQL/MariaDB version, the active theme (slug, version, available update, whether automatic updates are on), the active plugins (file name such as akismet/akismet.php, version, available update, whether automatic updates are on, up to 200), the number of inactive plugins and the inactive plugins themselves (file name, version, available update, whether automatic updates are on, up to 50), the number of users per role, the number of fatal errors and warnings added to debug.log, the debug settings (whether WP_DEBUG, WP_DEBUG_DISPLAY and WP_DEBUG_LOG are on), the size of debug.log in bytes and, only when it is inside the WordPress folder, its path from the site URL (such as wp-content/debug.log), the last published post time, the next scheduled post time and the number of scheduled posts, the number of WP-Cron events late by more than 1 hour and the longest delay, failed logins and lockouts in the last 24 hours (only with SiteGuard WP Plugin), the result of the daily file check (counts, and up to 10 relative paths for each kind in WordPress core (changed, missing, not in WordPress core) and for each plugin, 50 plugin paths in total, with the MD5 hash of each reported file that exists; or “turned off”), the result of the last automatic update (counts and the slugs of up to 5 failed items), and the automatic core update status (whether minor core updates are installed automatically, whether AUTOMATIC_UPDATER_DISABLED or DISALLOW_FILE_MODS is on or file changes are not allowed, the time, version and error code of the last failed automatic core update without the error message, whether DISABLE_WP_CRON is on, and the time of the next scheduled core update check).
What SiteBeacon does with the debug.log path: at most once a day after a report, SiteBeacon requests the first 512 bytes of that URL to see whether debug.log can be read from outside. Redirects are not followed, and the bytes read are only used for this check and are not stored.
Also received by SiteBeacon, as with any HTTP request: the IP address of your server and the User-Agent header that WordPress adds to its requests (it contains the WordPress version and your site URL).
When: once an hour by WP-Cron, and when you click “Send now” in Settings → SiteBeacon Reporter. Only while a token is saved.
Where: https://s-m.biz/siteb/api/v1/siteb/report (HTTPS POST, with your token in the Authorization header, 15 second timeout).
Terms of use: https://s-m.biz/siteb/lp/agreement
Privacy policy: https://s-m.biz/siteb/lp/privacy
WordPress.org checksum API – used by the daily file check.
What is sent: your WordPress version and locale (for the core checksums), and the slug and version of each plugin that is compared (for the plugin checksums). As with any HTTP request, WordPress.org also receives your server’s IP address and the WordPress User-Agent (WordPress version and site URL).
When: once a day, continuing 10 minutes later when the check does not finish in 20 seconds (up to 30 times a day). Only while a token is saved and the file check is not turned off.
Where: https://api.wordpress.org/core/checksums/1.0/ and https://downloads.wordpress.org/plugin-checksums/
Terms and privacy: https://wordpress.org/about/privacy/
WordPress.org update check – WordPress’s own check for plugin and theme updates.
Before each report, this plugin calls the WordPress functions wp_update_plugins() and wp_update_themes(). WordPress contacts WordPress.org only when it has not checked within the last 12 hours (or when installed plugins or themes changed), and sends what it always sends for this check (installed plugins and themes with their versions, WordPress version, locale). This plugin does not add anything to that request; it only limits the wait to 8 seconds.
When: before a report is sent, only while a token is saved.
Where: https://api.wordpress.org/plugins/update-check/ and https://api.wordpress.org/themes/update-check/
Terms and privacy: https://wordpress.org/about/privacy/
