PRTG P19 – Monitor UniFi Controller Using PRTG (Step-by-Step Guide)

In a production network, monitoring the UniFi Controller is critical. If the controller stops responding, devices may still pass traffic, but you lose centralized management, visibility, and configuration control.

In this guide, you will learn how to Monitor UniFi Controller using PRTG in a clean and efficient way. The goal is simple:

Determine whether the controller is actively serving device administration and information.

This setup focuses only on essential monitoring points to avoid unnecessary load while ensuring maximum visibility.

We will configure:

• HTTP availability monitoring

• Critical port monitoring

• Best practices for UniFi infrastructure visibility

Let’s begin.

🎯 Monitoring Objective

The main objective when you Monitor UniFi Controller is:

• Ensure the Web UI is accessible

• Ensure device inform service is alive

• Detect Java crashes

• Detect web service hangs

• Confirm controller availability

We are not monitoring CPU or memory in this guide.
We are monitoring controller service functionality.

🟢 #1 HTTP v2 Sensor

The most important sensor when you Monitor UniFi Controller is HTTP v2.

Configuration

Add an HTTP v2 sensor with the following settings:

• URL: https://IP:8443

Replace IP with the actual UniFi Controller IP address.

What to Check

Inside the HTTP v2 sensor, monitor:

• Response OK (200)

• Response time

Why This Is Important

This sensor is extremely useful for detecting:

• Web service hangs

• Java crashes

• Controller service failures

• SSL issues

If the HTTP sensor fails:

• The UniFi Web UI is unavailable

• Admin access is lost

• API calls may stop functioning

Even if the server is still powered on, HTTP failure means the controller is not serving properly.

This is the most direct way to Monitor UniFi Controller service health.

🟡 #2 Port Monitoring

In addition to HTTP monitoring, port monitoring ensures the controller services are listening correctly.

Add a Port sensor in PRTG.

Critical Ports to Monitor

🔹 TCP 8443 – UniFi Web

Purpose:

• Confirms the web server process is alive

• Ensures the UniFi Web interface is reachable

If TCP 8443 is closed:

• Web UI is down

• HTTPS service is not running

🔹 TCP 8080 – Inform Port

Purpose:

• Handles device inform communication

• Required for device adoption and management

Loss of TCP 8080 means:

• Devices cannot communicate with the controller

• Loss of device management

• Adoption failures

• Configuration push failures

This port is critical for production environments.

Configuration Path in PRTG

Go to:

Network Infrastructure → Port

Add:

• TCP 8443

• TCP 8080

Similarly configure both ports.

There is no need to set thresholds for the two ports.

Port monitoring is binary:

• Open = Service alive

• Closed = Service down

🧠 Understanding Failure Scenarios

When you Monitor UniFi Controller properly, you can quickly diagnose problems.

Scenario 1 – HTTP Fails but Port 8443 Open

Possible causes:

• Java process hanging

• Application-level failure

• SSL or certificate issue

Scenario 2 – Port 8080 Closed

Impact:

• Devices go offline in controller

• Inform communication broken

• Network changes not applied

Scenario 3 – All Sensors Down

Possible causes:

• Server powered off

• Network outage

• Firewall blocking monitoring

This structured approach allows you to identify the exact failure layer.

🚀 Why This Monitoring Design Works

Many administrators over-monitor UniFi.

They add:

• CPU

• Memory

• Disk

• Process monitoring

But in reality, to Monitor UniFi Controller effectively, you only need to ensure:

• Web service works

• Inform port works

This keeps:

• PRTG lightweight

• Monitoring clean

• Alerts meaningful

• Infrastructure scalable

Minimal monitoring, maximum clarity.

📌 Best Practices

When deploying UniFi monitoring in production:

✅ Use HTTPS URL with correct IP
✅ Monitor both 8443 and 8080
✅ Avoid unnecessary sensors
✅ Keep alerting simple
✅ Test failure scenarios manually

You can simulate:

• Stop UniFi service

• Block port 8080

• Restart Java

Then confirm PRTG detects the issue correctly.

🎯 Final Thoughts

To properly Monitor UniFi Controller, you do not need complex configurations.

You only need:

• HTTP v2 for application availability

• TCP 8443 for web service

• TCP 8080 for device management

This method ensures:

• Early detection of controller failure

• Protection of device management

• Clear and actionable alerts

With this setup, your UniFi Controller monitoring is clean, efficient, and production-ready.