Integrating Zabbix With Your MikroTik WISP Network

Zabbix is a powerful monitoring platform, and many SA WISPs already have it running. But getting proper MikroTik wireless monitoring in Zabbix requires custom SNMP OIDs, template creation, and trigger configuration that most WISP operators don't have time to figure out.

The Zabbix + MikroTik Challenge

Out of the box, Zabbix's MikroTik templates give you basic SNMP monitoring — CPU, memory, interface traffic. But WISPs need more:

• Wireless signal strength per client — not just aggregate interface stats
• CCQ (Client Connection Quality) — the metric that actually predicts service issues
• Automatic host creation — when you add a new device, Zabbix should know about it
• Meaningful triggers — "CCQ dropped below 60%" is more useful than "ICMP ping failed"

SNMP OIDs That Matter

For MikroTik wireless monitoring via SNMP, these are the key OIDs:

# Wireless registration table
1.3.6.1.4.1.14988.1.1.1.2.1.3  # Signal strength (dBm)
1.3.6.1.4.1.14988.1.1.1.2.1.19 # TX CCQ
1.3.6.1.4.1.14988.1.1.1.2.1.20 # RX CCQ

# Interface traffic
1.3.6.1.2.1.31.1.1.1.6  # ifHCInOctets
1.3.6.1.2.1.31.1.1.1.10 # ifHCOutOctets

The Setup Grind

To properly monitor a 100-device MikroTik network in Zabbix, you typically need to:

1. Enable SNMP on every MikroTik device (community string, allowed IPs)
2. Create or import MikroTik wireless templates with the right OIDs
3. Add each device as a Zabbix host (or set up auto-discovery rules)
4. Configure triggers for signal thresholds, CCQ drops, and interface errors
5. Set up actions for email/SMS alerts
6. Build dashboards to visualize the data

This works, but it's a full day's work for someone who knows Zabbix well. And it needs maintenance as you add devices.

How Connexa Simplifies This

Connexa integrates with your existing Zabbix server natively:

• Auto-sync devices — devices discovered in Connexa are automatically created as Zabbix hosts with the correct templates
• Trigger management — create and manage Zabbix triggers from the Connexa UI without touching the Zabbix frontend
• Unified dashboard — see Zabbix alerts alongside Connexa's own wireless monitoring data
• CCQ tracking — Ubiquiti CCQ values pulled via SNMP and displayed per-device

You keep Zabbix as your monitoring backend, but Connexa handles the MikroTik-specific automation and provides a cleaner operator interface.