Configure Plesk 360 Monitoring Alerts: A Step‑by‑Step Guide

Running a website or application on a VPS or dedicated server requires constant attention to server health. Even a brief CPU spike or a sudden loss of disk space can affect user experience and your business. Plesk 360 Monitoring provides a built‑in way to watch key metrics, send alerts, and analyse logs without installing third‑party tools.

Why use Plesk 360 Monitoring?

The 360 Monitoring dashboard combines performance graphs, resource thresholds, and log‑analysis utilities in a single interface. Its main benefits are:

• Real‑time visibility of CPU, RAM, disk I/O, and network traffic.
• Customisable alerts delivered via email or webhook.
• Integrated log analyser for Apache/Nginx, mail, and system logs.
• Zero‑extra licensing for Plesk customers – the features are included in the core installation.

Prerequisites

Before you begin, ensure you have:

1. A Plesk 360 Monitoring license activated on the server.
2. Root or sudo access to the underlying operating system.
3. An email address that will receive alert notifications.
4. Basic familiarity with the Plesk UI.

1. Enabling the Monitoring extension

The extension is bundled with Plesk but may be disabled by default. Install the required packages for your OS and restart the Plesk service.

Debian / Ubuntu (apt)

# Update package lists
sudo apt update

# Install the monitoring extension (if not already present)
sudo apt install plesk-monitoring

# Restart the Plesk service to load the extension
sudo service psa restart

AlmaLinux / Rocky Linux / RHEL (dnf)

# Refresh repository metadata
sudo dnf check-update

# Install the monitoring extension
sudo dnf install plesk-monitoring

# Restart the Plesk service
sudo systemctl restart psa

On Windows Server the extension is added through the Plesk installer UI; run the installer, select Monitoring, and complete the wizard.

2. Configuring resource thresholds

Thresholds define when Plesk should trigger an alert. You can set separate limits for CPU, memory, disk usage, and network traffic.

1. Log in to Plesk and go to Tools & Settings > Monitoring.
2. Open the Settings tab.
3. Under Resource thresholds, adjust the sliders or enter numeric values:
   • CPU usage – e.g., 80 % warning, 95 % critical.
   • Memory usage – e.g., 75 % warning, 90 % critical.
   • Disk space – set a percentage or absolute GB value.
   • Network traffic – useful for detecting DDoS or bandwidth caps.
4. Save the changes.

These thresholds are stored in /etc/psa/monitoring/thresholds.conf on Linux. You may edit the file directly and then reload the service with sudo service psa restart (Debian/Ubuntu) or sudo systemctl restart psa (AlmaLinux family).

3. Setting up alert notifications

After defining thresholds, configure how you want to be notified. Plesk supports email alerts out of the box and can also call a webhook for integration with Slack, Microsoft Teams, or custom scripts.

Configure email alerts

1. In the Monitoring dashboard, open the Alerts tab.
2. Click Add Alert and choose the resource (CPU, RAM, etc.).
3. Enter the recipient email address, a subject line, and an optional message template.
4. Select the severity level (Warning, Critical) that should trigger the email.
5. Save the alert.

Configure a webhook (optional)

1. Still under the Alerts tab, click Add Webhook.
2. Provide the webhook URL (e.g., https://hooks.slack.com/services/…).
3. Select the JSON payload format; Plesk includes fields such as resource, value, and timestamp.
4. Choose which severity levels should fire the webhook.
5. Test the webhook with the Send Test button, then save.

4. Enabling the log analyser

The log analyser scans common log files, extracts error patterns, and presents them in an easy‑to‑read table. It works with Apache, Nginx, mail logs, and system logs.

1. Navigate to Tools & Settings > Log Analyzer.
2. Click Enable Log Analyzer. The service will start indexing existing logs; this may take a few minutes depending on log size.
3. After indexing, view summaries under Logs > Log Analyzer. Use the filter bar to narrow results by domain, date range, or severity.

Customising log‑parsing rules

If your applications write to non‑standard log files, add a custom parser:

1. In the Log Analyzer page, click Custom Parsers > Add Parser.
2. Provide the full path to the log file (e.g., /var/log/myapp/app.log).
3. Select the log format (plain text, JSON, or custom regex).
4. Define the regex that extracts the timestamp, level, and message. Example for a simple format:

   ^\[(?[^]]+)\]\s+(?INFO|WARN|ERROR)\s+:\s+(?.*)$

5. Save and let the analyser re‑index the file.

5. Automating routine checks with cron

While Plesk continuously monitors resources, you may want a daily summary report emailed to you. The script below generates a CSV snapshot of the last 24 hours and sends it.

Debian / Ubuntu (apt)

# Create the script
sudo tee /usr/local/bin/plesk-monitor-report.sh > /dev/null <<'EOF'
#!/bin/bash
# Export monitoring data to CSV
/usr/local/psa/bin/monitoring --export csv > /tmp/monitoring_report.csv

# Email the report (mailutils must be installed)
echo "Daily Plesk monitoring report" | mail -s "Plesk Monitoring Report" -a /tmp/monitoring_report.csv your@email.com
EOF

# Make it executable
sudo chmod +x /usr/local/bin/plesk-monitor-report.sh

# Install mailutils if needed
sudo apt install -y mailutils

# Add a daily cron job at 07:00
sudo crontab -l | { cat; echo "0 7 * * * /usr/local/bin/plesk-monitor-report.sh"; } | sudo crontab -

AlmaLinux / Rocky Linux / RHEL (dnf)

# Create the script
sudo tee /usr/local/bin/plesk-monitor-report.sh > /dev/null <<'EOF'
#!/bin/bash
/usr/local/psa/bin/monitoring --export csv > /tmp/monitoring_report.csv
echo "Daily Plesk monitoring report" | mail -s "Plesk Monitoring Report" -a /tmp/monitoring_report.csv your@email.com
EOF

# Make it executable
sudo chmod +x /usr/local/bin/plesk-monitor-report.sh

# Install mailx (provides the mail command)
sudo dnf install -y mailx

# Register a daily cron job
sudo crontab -l | { cat; echo "0 7 * * * /usr/local/bin/plesk-monitor-report.sh"; } | sudo crontab -

On Windows Server you would create a PowerShell script using Get-PleskMonitoringData (available via the Plesk PowerShell module) and schedule it with Task Scheduler.

6. Verifying everything works

After configuring thresholds, alerts, and the log analyser, run a quick test:

1. Trigger a fake CPU alert: On Linux, run yes > /dev/null & to load the CPU, then watch the Monitoring dashboard. When usage crosses the warning level, you should receive an email or webhook notification.
2. Generate a log entry: Append a line to /var/log/apache2/error.log (or the Windows equivalent) that matches an error pattern, then open the Log Analyzer to confirm the entry appears.
3. Check the daily report: After the next scheduled run, verify that the CSV attachment arrived and contains recent metric rows.

If any step fails, review the relevant log files:

• Linux: /var/log/plesk/panel.log and /var/log/plesk/monitoring.log
• Windows: C:\Program Files (x86)\Plesk\admin\logs\panel.log

Conclusion

Effective monitoring is the backbone of a reliable hosting environment. By using Plesk 360 Monitoring you gain real‑time insights, automated alerts, and powerful log analysis without external services. The steps above walk you through enabling the extension, setting thresholds, configuring email or webhook notifications, activating the log analyser, and automating daily reports. With these safeguards in place, you can focus on growing your website or application while Plesk keeps an eye on server health.