Is it possible to get the JSON for the example dashboard included?

Thanks

Hey

I was just wondering if you'd be willing to set up an automated build on hub.docker.com for this repo :)

There are a few people who have forked the repo and set up their own builds, but that relies on them pulling in circles from here.

Cheers,
Chris

Hello,

I run a setup where I have different user groups seperated by SSIDs on the same site. I'd really like to have a feature to show the number of clients on each SSID, e. g. :

unifi_stations{ssid="A"} 110
unifi_stations{ssid="B"} 23

For my usecase a further differentation in sites would no be necessary. But the more sustainable implementation would probably be:

unifi_stations{site="X",ssid="A"} 110
unifi_stations{site="X",ssid="B"} 23
unifi_stations{site="Y",ssid="A"} 12
unifi_stations{site="Y",ssid="C"} 16

Thanks for considering!

Would be nice if this was exposed. (enhancement)

I think this is great and thank you for it. I read the other issue regarding this topic but it sounds like there's some confusion on how we can get this setup...

@mdlayher Since you own the repo you need to link it in the Docker hub: https://hub.docker.com/r/mdlayher/

You can just follow the steps here to get this repository on the hub and set up with automated builds! It should hopefully only take a few minutes and once it's setup you won't really need to worry about it.

I see a lot of forks of this repository on Docker Hub but they are months behind in terms of PR's and such. It'd be a lot more straightforward to just link this to the Docker Hub directly.

My apologies for opening a separate issue for this, but it seems the other one is closed and is not getting any attention.

This is likely purely because I'm new to building and go, but I'm getting tripped up on building from this project. I've cloned the project, but when I use make I'm getting this:

sysadmin@prometheus-srv:~/docker/unifi_exporter$ make
go build ./cmd/unifi_exporter
cmd/unifi_exporter/main.go:13:2: cannot find package "github.com/mdlayher/unifi" in any of:
	/usr/local/go/src/github.com/mdlayher/unifi (from $GOROOT)
	/home/sysadmin/work/src/github.com/mdlayher/unifi (from $GOPATH)
cmd/unifi_exporter/main.go:14:2: cannot find package "github.com/mdlayher/unifi_exporter" in any of:
	/usr/local/go/src/github.com/mdlayher/unifi_exporter (from $GOROOT)
	/home/sysadmin/work/src/github.com/mdlayher/unifi_exporter (from $GOPATH)
cmd/unifi_exporter/main.go:15:2: cannot find package "github.com/prometheus/client_golang/prometheus" in any of:
	/usr/local/go/src/github.com/prometheus/client_golang/prometheus (from $GOROOT)
	/home/sysadmin/work/src/github.com/prometheus/client_golang/prometheus (from $GOPATH)
Makefile:4: recipe for target 'build' failed
make: *** [build] Error 1

would you mind helping out a newer user on what I'm missing here?

When the password is specified on the command like it's very easy for unprivileged users to see the password. A config file should be used for at least the password, and it'd be nice to be able to use a config file for the other options as well.

unifi_exporter infrequently stops working and just responds with:

An error has occurred:

error collecting metric Desc{fqName: "unifi_devices", help: "Total number of devices", constLabels: {}, variableLabels: [site]}: failed to parse inform IP:

on the telemetry port.

AFACT the issue seems to occur when there are devices which are pending approval. The JSON object for this device returned by the unifi API does not have a inform_ip property.

So, the device parsing seems to be too strict.

I can export different sites on the same controller with the "-unifi.site" option.

Without the -unifi.site option, only one site (the first I created on the controller) is exported, but all sites should be scraped.

As a workaround I got several unifi_exporter processes running, one for each site.

thanks for having a look into it!

Now that we are able to differentiate wired or wireless stations, these labels should be exposed for further filtering via Prometheus labels.

I'm very new to go, is there a detailed guide on how to get started?

2017/06/30 08:51:28 [INFO] successfully authenticated to UniFi controller
2017/06/30 08:51:28 Starting UniFi exporter on ":9130" for site(s): Thuis
2017/07/01 02:58:17 [ERROR] failed collecting station metric Desc{fqName: "unifi_stations", help: "Total number of stations (clients)", constLabels: {}, variableLabels: [site]}: Get https://192.168.1.30:8443/api/s/default/stat/sta: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
2017/07/01 02:58:22 [ERROR] could not initialize UniFi client: failed to authenticate to UniFi Controller: Post https://192.168.1.30:8443/api/login: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
2017/07/01 13:48:17 [ERROR] failed collecting device metric Desc{fqName: "unifi_devices", help: "Total number of devices", constLabels: {}, variableLabels: [site]}: Get https://192.168.1.30:8443/api/s/default/stat/device: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2017/07/01 13:48:21 [INFO] successfully authenticated to UniFi controller
2017/07/02 08:47:20 failed to create client: failed to authenticate to UniFi Controller: Post https://192.168.1.30:8443/api/login: dial tcp 192.168.1.30:8443: getsockopt: connection refused

This happens when the machine running things is rebooted, takes a while before Unifi starts, the exporter is up much faster.

Probably needs a retry loop somewhere.

Hi! First, thanks for the exporter!

I'd love to be able to graph wifi interference. (Perhaps with labels for the access point and channel.) I haven't checked if the unifi api supports it.. but I thought I'd post the idea here and see if anyone else has time to dig in more..

Cheers,

Geoff

Exporter dies after unexpectedly receiving a status code 400 from a Unifi Cloud Key.

Unifi 5.4.15
Cloud Key firmware 0.6.4

# ./unifi_exporter -unifi.addr https://unifi-key:8443/ -unifi.username unifiexporter -unifi.password password -unifi.insecure 2017/05/12 14:30:09 failed to create client: failed to authenticate to UniFi Controller: unexpected HTTP status code: 400

I'm getting the following error after upgrading the controller to 5.5.8

[ERROR] failed collecting device metric Desc{fqName: "unifi_devices", help: "Total number of devices", constLabels: {}, variableLabels: [site]}: json: cannot unmarshal number 3.733721026E9 into Go value of type int64

failed to authenticate to UniFi Controller: expected "application/json;charset=UTF-8" content type, but received "application/json"

thanks

Could someone provide some guidance on how to modify unifi_exporter for this? what files/functions should I look at?

An error has occurred:

error collecting metric Desc{fqName: "unifi_stations", help: "Total number of stations (clients)", constLabels: {}, variableLabels: [site]}: invalid MAC address

Controller v5.3.7. What version on your running?

When trying to accesss /metrics, getting this error:

An error has occurred during metrics collection:

error collecting metric Desc{fqName: "unifi_devices", help: "Total number of devices", constLabels: {}, variableLabels: [site]}: json: cannot unmarshal number 8.4287193168E10 into Go value of type int64

Controller 5.6.19

I'd like to be able to do like the chart below. I don't see these metrics. Is there any chance they could be added?

I am trying to make sense of the metrics and... seeing unexpected things. Any chance you could export your grafana dashboard form the readme as a json, so I can see how you used them?

This should probably go on package unifi, but since more folks follow the issues here:

Now that I have a unifi switch, I'd like to rework some metrics and remove some of the more hacky workarounds we have in place now. This issue will track that work.

I use the default self-signed cert on my unifi server (version 5.1.1) and I get this error even though I have specified the -unifi.insecure flag. Using version 0.2.0 of the exporter.

/opt/unifi_exporter/0.2.0/unifi_exporter -telemetry.addr 127.0.0.1:9130 -unifi.addr https://192.168.4.2:8443/ -unifi.insecure -unifi.username jeff -unifi.password xxxxx
2016/09/07 23:29:55 failed to create client: failed to authenticate to UniFi Controller: Post https://192.168.4.2:8443/api/login: remote error: tls: handshake failure