-
Notifications
You must be signed in to change notification settings - Fork 54
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
No Field unifiVapCcq, No Client Connection Quality (Unifi AP Dashboard) #19
Comments
My APs running 3.9.54.9373 do show that value:
|
Oh! But I only see it on my old UAP. My newer UAP-AC-Lites don't provide it. |
CCQ was removed by UBNT from UniFi AP firmwares and I haven't gotten to update the dashboards yet. CCQ was generally never actually useful nor correct with UAPs anyway. . . |
I am getting data for all panels except for 'Client Connection Quality'. I see the query begins with:
SELECT last(\"unifiVapCcq\") / 10 FROM \"unifiVapTable\"
However I have no unifiVapCcq field in unifiVapTable. Here is a sample write point (some values obscured):
> unifiVapTable,agent_host=unifi01,host=host001,unifiVapName=ath0,unifiVapRadio=ng unifiVapBssId="80:2b:a2:3a:44:2",unifiVapChannel=11i,unifiVapEssId="ssid001",unifiVapExtChannel=0i,unifiVapNumStations=3i,unifiVapRxBytes=3226148884i,unifiVapRxCrypts=108140i,unifiVapRxDropped=108610i,unifiVapRxErrors=108610i,unifiVapRxFrags=0i,unifiVapRxPackets=22051767i,unifiVapTxBytes=1317084149i,unifiVapTxDropped=62653i,unifiVapTxErrors=0i,unifiVapTxPackets=38486213i,unifiVapTxPower=20i,unifiVapTxRetries=1305891i,unifiVapUp=1i,unifiVapUsage="user" 1543803019000000000
I'm unsure if the missing comma following unifiVapRadio=ng is intentional (could this be the separation between tags and fields?). This is consistent across all the write points I see.
I am using the same MIBS, including UBNT-UniFi-MIB, as in this repository.
This could be something missing in the inputs. This could also be SNMP on my APs (2x UAP-AC-Lite 3.9.54.9373, GEN2). I could use help here.
The text was updated successfully, but these errors were encountered: