-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monitoring an UDM from WAN side #112
Comments
I would use SNMP. or try using the unpoller solution with Grafana and influxDB. Depends upon what you are trying to monitor. Lawrence |
So Zabbix is on the WAN from the UDM's perspective? Any option to create a site to site VPN? That is what I do everywhere.. |
Unifi doesnt really have snmp, you can install it on the UDMs but theres a chance an update will break the setup. We would like to monitor the UDM itself, WAN port(s) uptime, status, updates etc. It is available in the Unifi API but we cant reach the API from public… |
Zabbix is hosted elsewhere (Azure). Could work, but we have too many in the field, we also wouldn’t want to chain all out clients together if that makes sense, so we thought doing it over WAN with conditional access policies (port forwarding to single public IP). Unifi does have an API it can work with, but havent been able to reach it from public, only from internally. |
@IanICTSG |
Yea UnPoller looks great, but the boss wants to have multiple platforms monitored in one dashboard IE Mikrotik, Fortigate and in this case Unifi. Right now they are monitored with a simple ping, Not sure if Grafana supports SNMP monitoring, Fortigate API and simple ICMPs besides the UDM API shown here. I do have an Unifi controller that I could monitor with the Unifi API in Zabbix, but its just the UDMs that I cant monitor. |
so if you can get to a controller from the outside, you can also get to the UDM's self hosted controller no? should work the same.. |
How would we go about monitoring an UDM from the WAN side using Zabbix?
The text was updated successfully, but these errors were encountered: