Pro Monitoring & Alerts compares environment checks over time and can notify staff when results worsen. It is separate from the cached Report and from file-integrity monitoring.

Review schedule and destinations

1. Confirm PD Guard Pro is active.
2. Open Settings and review Pro: scheduled monitoring & alerts.
3. Set Pro: monitoring interval (hours) within its range of 1–168.
4. Review Alert recipient email(s) and any intended Pro webhook destination, then save.
5. Open Monitoring & Alerts and compare Status, Checks, Last check, Alerts to and Webhook.

The scheduler can have a job-specific interval override. The monitoring panel attempts to show the effective job interval, so review Environment monitoring in the PD Modules jobs view as well as the module setting. The platform cron still needs to run.

Establish the first comparison

The first stored monitoring run establishes a comparison point. Existing failures in that first result do not automatically become regression emails. Review them directly rather than waiting for an alert that requires a later change.

Opening the monitoring panel runs fresh environment checks for its live cards but does not itself create a stored monitoring run. Run check now does create a run and can send alerts. It bypasses the normal due-time wait and can run even while scheduled monitoring is paused; it is not a harmless preview.

Check the outcome

Compare the stored run time and details after the intended check. A scheduler summary alone is not proof that every measurement succeeded or a message reached its destination. File-integrity and failed-login jobs have their own settings and schedules; pausing environment monitoring does not switch them all off.

See the PD Guard WHMCS guide for related tasks, or explore PD Guard.