SiteBeacon Reporter
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
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 and available updates (up to 200)
- Number of inactive plugins 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
- 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 and relative paths only)
- The result of the last automatic update (counts and slugs only)
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
