PRTG – P14 How to Configure Email Alerts in PRTG Network Monitor

Monitoring without notifications is meaningless.
If your system goes down and you don’t receive an alert, your monitoring setup has failed its purpose.

In this guide, you will learn how to properly configure Email Alerts in PRTG so that every critical event triggers an instant notification. We will configure SMTP, define recipients, create a notification template, and bind it to triggers for real-world testing.

This is a production-ready configuration suitable for enterprise environments.

📌 Why Email Alerts in PRTG Matter

Email notifications allow you to:

• Get real-time alerts when devices go DOWN

• Monitor infrastructure remotely

• Reduce incident response time

• Prevent long service outages

Without properly configured Email Alerts in PRTG, you are simply collecting metrics — not managing infrastructure.

#1️⃣ STEP 1: Configure SMTP (MANDATORY)

Before PRTG can send email alerts, you must configure an SMTP server.

Go to:

You have three common options:

🔹 Option 1: Gmail SMTP

Note: You must use your Gmail App Password.

Important:

• Enable 2FA on Gmail

• Generate an App Password

• Use the App Password instead of your normal Gmail password

🔹 Option 2: Microsoft 365 SMTP

Note: You must enable SMTP Authentication for the user sending notifications.

Ensure:

• SMTP AUTH is enabled for the mailbox

• Modern authentication policies allow SMTP

🔹 Option 3: Internal Mail Server

If your organization has its own mail server:

After configuration, click:

Enter a recipient email address for testing, for example:

If the test email is received successfully, your SMTP configuration is correct.

#2️⃣ STEP 2: Declare Recipient Email Address

Now we define who will receive alerts.

Navigate to:

Here you:

• Create a new contact

• Enter the recipient email address

• Save configuration

This step ensures PRTG knows the valid notification targets.

Without declaring contacts, email alerts will not be delivered properly.

#3️⃣ STEP 3: Create or Use Email Notification Template

Now we define the content of the email alert.

Go to:

You can:

• Create a new template

• Or use a pre-made template

🔹 Create New Email Template

Click Add Notification Template

Configure the email section.

📝 Subject (Standard – Easy to Read)

This subject format ensures:

• Device name is visible

• Sensor name is clear

• Status (Down, Warning, Up) is shown immediately

In the recipient field:

Enter the email addresses separated by commas.

Example:

This ensures multiple team members receive the alert simultaneously.

Save the template after configuration.

#4️⃣ STEP 4: Assign Email to Trigger (IMPORTANT)

This is the most critical step.

👉 Email will only be sent when the trigger is triggered.

Many administrators configure SMTP and templates but forget to attach them to triggers.

Open the device or sensor you want to monitor.

Go to:

Choose:

• When sensor state is Down

• When sensor state is Warning

• When sensor value exceeds threshold

Select the email template you created earlier.

Save configuration.

Now Email Alerts in PRTG are fully active.

🧪 Real Test – Shutdown VM (Demo)

To verify the configuration works:

Test demo shutdown VM Unifi

When the VM goes offline:

• Sensor status changes to Down

• Trigger condition activates

• Email notification is sent immediately

If the email arrives in your inbox, the configuration is successful.

🔎 Best Practices for Email Alerts in PRTG

To optimize your alert system:

• Avoid sending alerts for non-critical sensors

• Use different templates for Warning and Down

• Set delay triggers to avoid alert storms

• Regularly test SMTP functionality

Well-configured Email Alerts in PRTG improve operational visibility and reduce downtime dramatically.

🏁 Conclusion

Properly configuring Email Alerts in PRTG transforms your monitoring system into a proactive incident response tool.

The full workflow includes:

1. Configure SMTP

2. Declare notification contacts

3. Create email templates

4. Assign triggers to sensors

Once completed, your infrastructure becomes self-reporting.
Instead of waiting for users to complain, you will know immediately when something goes wrong.

This is the difference between passive monitoring and professional network management.