# Notifications
The Notifications tab allows you to configure alerts for your PanelAlpha Engine server so you stay informed about important events.
# High Disk Usage Alert
Monitor disk space consumption on your PanelAlpha Engine server with the High Disk Usage Alert.
# Configuration
- Toggle Switch — enable or disable the high disk usage alert
- Alert Threshold — alert is sent when disk usage reaches or exceeds 90%
- Information Icon — shows tooltip: "Alert will be sent when 90% or more of disk usage is detected"
# How It Works
When enabled, the system monitors disk space and automatically sends an alert when usage reaches or exceeds 90%. This helps you:
- Prevent service disruptions due to full disks
- Take proactive action before running out of space
- Plan for storage capacity expansion
# Responding to Disk Usage Alerts
When you receive a high disk usage alert, take the following actions:
Identify large files and directories:
- Check log files for excessive size.
- Review backup storage location.
- Identify WordPress instances using the most space.
Free up disk space:
- Clean up old log files.
- Remove unnecessary backups.
- Delete unused WordPress instances.
- Clear temporary files.
Plan for capacity:
- Consider upgrading storage.
- Implement automatic log rotation.
- Configure backup retention policies.
# High CPU Usage Alert
Monitor CPU utilization on your PanelAlpha Engine server with the High CPU Usage Alert.
# Configuration
- Toggle Switch — enable or disable the high CPU usage alert
- Alert Threshold — alert is sent when CPU usage remains consistently high; configure the threshold in the notification settings below
- Information Icon — shows tooltip with CPU usage threshold details
# How It Works
When enabled, the system monitors CPU usage and automatically sends an alert when utilization exceeds critical levels for an extended period. This helps you:
- Detect resource-intensive processes affecting performance
- Identify potential security threats (cryptominers, DDoS attacks)
- Prevent service degradation due to CPU overload
- Optimize WordPress instance resource allocation
# Responding to High CPU Alerts
When you receive a high CPU usage alert, investigate the following:
Identify CPU-intensive processes:
- Check running WordPress instances for unusual activity.
- Review web server processes (Apache, Nginx, LiteSpeed).
- Look for runaway PHP processes.
- Check for malware or compromised accounts.
Take corrective action:
- Restart problematic services if necessary.
- Optimize WordPress plugins causing high CPU usage.
- Enable caching to reduce CPU load.
- Consider upgrading server resources if consistently high.
Monitor performance:
- Review performance graphs in the Details tab.
- Check individual instance resource usage.
- Implement resource limits if needed.
# High RAM Usage Alert
Monitor memory consumption on your PanelAlpha Engine server with the High RAM Usage Alert.
# Configuration
- Toggle Switch — enable or disable the high RAM usage alert
- Alert Threshold — alert is sent when memory usage reaches critical levels; configure the threshold in the notification settings below
- Information Icon — shows tooltip with RAM usage threshold details
# How It Works
When enabled, the system monitors RAM usage and automatically sends an alert when memory consumption exceeds safe operating levels. This helps you:
- Prevent out-of-memory (OOM) errors that crash services
- Identify memory leaks in applications
- Ensure optimal server performance
- Plan for memory capacity upgrades
# Responding to High RAM Alerts
When you receive a high RAM usage alert, take the following actions:
Identify memory-hungry processes:
- Check PHP-FPM memory usage.
- Review MySQL/MariaDB memory consumption.
- Identify WordPress instances with high memory usage.
- Look for memory leaks in long-running processes.
Free up memory:
- Restart services to clear memory leaks.
- Optimize database queries and indexes.
- Reduce PHP memory limits where appropriate.
- Clear object caches if necessary.
Optimize configuration:
- Tune PHP-FPM pool settings.
- Adjust MySQL/MariaDB buffer pool sizes.
- Implement WordPress object caching (Redis/Memcached).
- Consider upgrading server RAM if consistently high.
Note: Metrics are collected every 5 seconds and retained for 90 days. Alert thresholds are configured in the notification settings.
# Saving Notification Settings
After configuring any alerts on this page:
- Toggle the desired alert switches (Disk, CPU, or RAM).
- Click the "Save Changes" button (green button at the bottom).
- Changes are applied immediately to the server.
Important: You can enable multiple alerts simultaneously. Each alert operates independently and triggers based on its specific threshold.
# Notification Recipients
To configure who receives notification alerts from this server:
- Navigate to Configuration > System Configuration > Notifications.
- Configure email addresses for notification recipients.
- Set up notification preferences and alert frequency.
- Save the configuration.
All alerts from this PanelAlpha Engine server are sent to the email addresses configured in the system-wide notification settings.
# Alert Best Practices
# Recommended Configuration
For optimal server monitoring, we recommend:
- Enable all three alerts (Disk, CPU, RAM) for comprehensive monitoring.
- Test alerts after configuration to ensure they are working properly.
- Configure multiple recipients to ensure alerts are not missed.
- Set up escalation procedures for critical alerts.
# Alert Frequency
PanelAlpha Engine implements smart alert frequency management:
- Throttling — alerts are not sent repeatedly for the same issue.
- Cooldown period — after an alert is sent, a cooldown period prevents alert spam.
- Resolution notification — optional notification when the issue is resolved.
# Monitoring Strategy
Proactive Monitoring:
- Enable alerts before issues occur.
- Regularly review performance graphs in the Details tab.
- Plan capacity upgrades based on trends.
Response Plan:
- Document standard response procedures for each alert type.
- Assign team members to respond to specific alert categories.
- Keep escalation contact information up to date.
Performance Optimization:
- Use alerts as early warning signs.
- Investigate root causes, not just symptoms.
- Implement preventive measures based on alert patterns.
# Troubleshooting Notifications
# Not Receiving Alerts
If you are not receiving alert notifications:
Check email configuration:
- Verify SMTP settings in PanelAlpha.
- Test email delivery from System Configuration.
- Check spam and junk folders.
Verify alert settings:
- Ensure alerts are enabled (toggle is ON).
- Confirm thresholds are being exceeded.
- Check that notification recipients are configured.
Review server logs:
- Check PanelAlpha logs for notification errors.
- Verify email sending logs.
- Look for SMTP connection issues.
# False Positive Alerts
If you are receiving too many alerts:
- Review threshold settings — consider if they are too sensitive.
- Optimize server performance — address underlying issues.
- Implement auto-scaling — for cloud-based deployments.
- Adjust monitoring intervals — balance responsiveness and alert fatigue.
# Bulk Disable / Alert History
To temporarily silence all alerts from a server, toggle off each alert switch (Disk, CPU, RAM) on this page and click "Save Changes". Re-enable them once the underlying issue is resolved.
Historical alert activity is surfaced through the PanelAlpha notification system and server logs. Review the notifications panel and the Engine's core container logs for past alert events.