What does WBmonitor do?
WBmonitor will periodically connect to your website and ask the installed module for a report on multiple things.
1. Changed files.
WBmonitor was originally created to detect changed files.
Changing files can be the result of (succesfull) hacking attempts, but because it checks everything it will also report installed or upgraded modules.
If you are the website owner and you installed something yourself you can simply ignore the report, on any other moment you might want to check if your customer did any installs or upgrades.
You can configure this test per monitor in this website to use (or not use) a checksum on all files.
Enabling this makes the detection of changes more reliable, but it will be much slower and it will use more resources on your server.
2. Changed pages in the database.
Changed pages are recorded whenever a page is modified or when a new page was created.
This might seem a little "much", but remember, a hacker can use a droplet or a code page to execute ay PHP code. It is just as "dangerous" as uploading files.
Also if you are a webdesigner that stays responsible for a created website you might want to be notified if your customer adds or removes content.
3. Additions to the php_error.log file (since WBmonitor v 1.3.0)
Since WebsiteBaker 2.8.3 SP7 (revision 1646) a logfile is used to report any errors in modules and/or templates.
These errors can be the result of bad modules or templates, but they could also be caused by external changes (like server upgrades) or even hacking attempts.
The monitor allows you to quickly check the last lines of this logfile, but optional it can also warn when any log entries were added since the previous check.
Note that this will send many reports if your website writes notices/warning in normal use.
For this reason, this setting is default set to "off".
4. The modules (versions) used in your website.
You can ask WBmonitor to also monitor the modules your website has installed.
There will be no reports by email for this, but you can simply find all installed modules and their versions. If other websites monitored by WBmonitor are using newer versions you will see a small notification of that fact. It is up to you to find and upgrade the newer version.
5. Old WebsiteBaker versions.
WBmonitor will warn you about old WebsiteBaker versions that are not safe to use.
You should always use the latest version, just to be safe.
Being a webdesigner myself with many WebsiteBaker installations I know it is a lot of work to upgrade all your customers websites as soon as a new version is available. Because of this, the trigger for this warning is set to any versions below WebsiteBaker 2.8.3 SP3 (revision 1640). A warning mail is sent once per week to help you to remember to upgrade this website.