The Problem: Reactive Monitoring Doesn’t Scale
You find out about 3CX problems one of two ways: you check manually, or a client calls. Neither scales.
Manual checks mean logging into each 3CX instance, eyeballing dashboards, and hoping you notice the disk that’s 92% full or the trunk that dropped overnight. Centralized monitoring changes that equation entirely. With five systems, maybe that works. With fifty, you’re not checking often enough to catch anything before it hurts.
Client calls mean the problem already happened. Call quality degraded, voicemail stopped working, the system went down. Now you’re in firefighting mode, and the client’s first question is always: “Didn’t you know about this?”
What Controvo Monitors
Controvo ships with monitors for the metrics that actually predict 3CX problems:
- CPU Utilization — Catch sustained high CPU before it affects call quality
- RAM Utilization — Identify memory pressure before the system starts swapping
- Disk Space Usage — Know when a backup drive or recording partition is filling up
- Network Latency — Detect connectivity issues between your monitoring point and the PBX
- Ping Jitter — Spot network instability that causes choppy audio
- License Expiration — Never get surprised by an expired 3CX license again
Each monitor is fully configurable. Set your own thresholds — CPU above 80% for 5 minutes, disk below 15%, license expiring within 30 days. You decide what matters for your environment.
How Alerting Works
A monitor without an alert is just a number. Controvo connects monitors to actions.
Build Your Own Alert Rules
Create an alert, pick a monitor, set the threshold, and choose what happens when it trips. Right now that means email notifications. The right people get told about the right problems on the right systems.
Apply to Individual Systems or Groups
You don’t have to configure alerts one system at a time. Apply them to groups — all production systems, all systems for a specific client, all systems in a region. When you add a new phone system to a group, it inherits the alerts automatically.
Alert Exclusions
Not every system needs every alert. Maybe a lab system runs hot and you don’t want CPU alerts for it. Exclusions let you fine-tune which systems trigger which alerts without creating dozens of one-off rules.
Why This Beats Checking Manually
The math is simple. If you check a system once a day and a problem develops at 9 AM, you might not see it until 9 AM tomorrow. That’s 24 hours of degraded service, or worse, downtime.
With threshold-based monitoring, the alert fires within the check interval. You know about the problem in minutes, not hours. And you know about it from an email in your inbox, not from a frustrated client on the phone.
The Scale Advantage
Manual checking takes time proportional to the number of systems. Fifty systems at two minutes each is over an hour and a half — every day, assuming you actually do it. Automated monitoring takes the same amount of time whether you have 5 systems or 500: zero.
Your team’s time goes to fixing problems instead of finding them.
From Alerts to Action
Monitors tell you something is wrong. Alerts tell the right people.
Controvo’s alerts integrate with ConnectWise PSA, so a triggered alert can automatically create a service ticket. The issue gets triaged, dispatched, and tracked in your existing workflow. When the monitor clears, the ticket gets updated. No manual ticket creation, no forgotten follow-ups.
Getting Started
Monitors and alerts are available now. Create your first monitor, set a threshold, attach an alert, and apply it to your phone systems. Already in the pilot? Log in and set it up. Not yet? Apply for the pilot to get early access.