Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Ubiquiti UDM-Pro API Monitoring

Hello,

We want to monitor a Ubiquiti UDM-Pro that does not support SNMP, I found the following post from @chad.every where he was able to pull the data via API

Ubiquiti API Monitoring - A different approach to polling

I imported the SAM templates and groups, I ran a test on the template and received the following error, does any one know what is missing or if there is another way to pull the details?

Find more posts tagged with

@ubiquiti

Accepted answers

chad.every

The scripts in those templates rely on two explicitly defined Node Custom Properties in your SW deployment.

API_Controller_Hostname (Unifi controller IP or hostname)
Site_Code (Set to 'default' if only using one Unifi site. If using multiple you need to find the reference to the site name in Unifi)

There is also a third Node Custom Properties, but I think this was required for the WAP tempaltes to filter by device in the Unifi API

MAC_Address

Here is an example screenshot from one of my Ubiquiti nodes in SW's.

All comments

chad.every

The scripts in those templates rely on two explicitly defined Node Custom Properties in your SW deployment.

API_Controller_Hostname (Unifi controller IP or hostname)
Site_Code (Set to 'default' if only using one Unifi site. If using multiple you need to find the reference to the site name in Unifi)

There is also a third Node Custom Properties, but I think this was required for the WAP tempaltes to filter by device in the Unifi API

MAC_Address

Here is an example screenshot from one of my Ubiquiti nodes in SW's.

truegodfather

Thank @chad.every I added the custom properties and ran the scan again, I now receive the following error, I did add the MAC Address for each AP

truegodfather

I ran a test on the WAP template and received this message

chad.every

Is the controller hostname custom property the hostname of the Unifi Controller? Looks like you have the hostname of the access point.

truegodfather

I updated the custom property with the correct hostname but I still receive the same error

Output: ==============================================
Statistic.State: -1
Message.State: Cannot bind parameter 'Uri'. Cannot convert value "https:// Group HQ:8443/api/login" to type "System.Uri". Error: "Invalid URI: The hostname could not be parsed."
Statistic.Total_Clients: -1
Message.Total_Clients: Cannot bind parameter 'Uri'. Cannot convert value "https://Group HQ:8443/api/login" to type "System.Uri". Error: "Invalid URI: The hostname could not be parsed."
Statistic.CPU_Usage: -1
Message.CPU_Usage: Cannot bind parameter 'Uri'. Cannot convert value "https://Group HQ:8443/api/login" to type "System.Uri". Error: "Invalid URI: The hostname could not be parsed."
Statistic.Memory_Usage: -1
Message.Memory_Usage: Cannot bind parameter 'Uri'. Cannot convert value "https://Group HQ:8443/api/login" to type "System.Uri". Error: "Invalid URI: The hostname could not be parsed."
Statistic.WiFi_Experience: -1
Message.WiFi_Experience: Cannot bind parameter 'Uri'. Cannot convert value "https://Group HQ:8443/api/login" to type "System.Uri". Error: "Invalid URI: The hostname could not be parsed."

truegodfather

chad.every

Its hard to say if the output is sanitized or not, but there are spaces in your hostname. It needs to be resolvable vis DNS or you can use the Unifi controller IP.