Steve Brunton

Yes, it does. What is your polling rate from prometheus? It doesn't do any sort of caching because it expects that your poll rate from Prometheus is what you want...

Oh, already add the go func per device thing already. I guess it's really just down to the other part then.

You can do a MAC address to registration mapping against the AP via the cap manager. I'm not sure how painful it would be to try to do the mappings...

This is a good idea. I haven't pointed my collector yet at the cloud switch because I don't really have a lot of stuff plugged into it. Let me see...

Thanks @klaper. I like this PR in practice, but how bad will it break all the existing configs out there in the wild?

That seems like a quick file time wise. Is that the correct IP address for the router? If so are you running this from within a docker container and routing/egress...

Are you getting an error message reported by the exporter?

What device and OS version? Building from `master` I get : ``` # TYPE mikrotik_dhcp_leases_active_count gauge mikrotik_dhcp_leases_active_count{address="x.x.x.x",name="router",server="default"} 72 mikrotik_dhcp_leases_active_count{address="x.x.x.x",name="router",server="dhcp1"} 0 ``` when I curl against it.

Do you have IPV6 configured and running? If not and you turn off dhcpv6 to false does it work?

It's probably something that should be implemented in the upstream Client API Library either via a long lived connection with a health checking mechanism and reconnect logic. I think even...