Not work 'Get Network Wireless Devices Latency Stats' API

SOLVED
Gwangjin
Here to help

Not work 'Get Network Wireless Devices Latency Stats' API

I was using the 'Get Network Wireless Devices Latency Stats' API and suddenly I can't get the result data.

1) I receive all 'latencyStat' as null.
2) There are 5APs in the network, but only 4APs are being received.

 

capture.png

 

 

 

 

 

 

 

 

 

 

 

 

 


Is it because of config?
If so, which config should I check?

 

Please let me know.

1 ACCEPTED SOLUTION

Accepted Solutions
sungod
Getting noticed

Re: Not work 'Get Network Wireless Devices Latency Stats' API

Hmmm, I just tested as it looks related to another API problem, it is indeed returning nulls, looks like a fault.

 

Below is cut & paste (part-masked serial numbers) from devnet test page https://developer.cisco.com/meraki/api-v1/#!get-network-wireless-devices-latency-stats with timespan 86400 on a network with active APs that clearly should have stats...

Response: 200  OK

 

 

Copy[
    {
        "serial": "Q3AJ-TC.......",
        "latencyStats": null
    },
    {
        "serial": "Q3AJ-BP.......",
        "latencyStats": null
    },
    {
        "serial": "Q3AJ-YW.......",
        "latencyStats": null
    },
    {
        "serial": "Q3AJ-TD.......",
        "latencyStats": null
    },
    {
        "serial": "Q3AJ-DE.......",
        "latencyStats": null
    }
]

 

 

It looks just like the problem that exists with the getNetworkWirelessDevicesConnectionStats call returning nulls...

 

https://community.meraki.com/t5/Developers-APIs/Has-getNetworkWirelessDevicesConnectionStats-stopped...

 

Note that both calls are requesting wireless stats network-wide, both are returning device IDs ok, but with nulls instead of the appropriate data, imo that suggests something is broken in the v1 API server that both calls rely on.

 

The getNetworkWirelessDevicesConnectionStats call has been broken since 6-7 January, that is over four months now.

 

Latest Meraki support feedback from internal teams is that "this issue is not treated with high priority".

 

Fyi the only workaround I found is to rewrite to use the equivalent v0 API call, but that's not a long term solution and of course it gets messy having to mix v0/v1 APIs in applications

 

Can any of the Meraki people say what expectation customers should have for v1 API calls being fixed?

 

View solution in original post

4 REPLIES 4
Inderdeep
Head in the Cloud

Re: Not work 'Get Network Wireless Devices Latency Stats' API

Gwangjin
Here to help

Re: Not work 'Get Network Wireless Devices Latency Stats' API

Thank you for your answer.

So, do I think 'latencyStats: null' equals zero?

Inderdeep
Head in the Cloud

Re: Not work 'Get Network Wireless Devices Latency Stats' API

Null is not the value you want to return and zero is not the same as null 

Regards
Inderdeep Singh
www.thenetworkdna.com
sungod
Getting noticed

Re: Not work 'Get Network Wireless Devices Latency Stats' API

Hmmm, I just tested as it looks related to another API problem, it is indeed returning nulls, looks like a fault.

 

Below is cut & paste (part-masked serial numbers) from devnet test page https://developer.cisco.com/meraki/api-v1/#!get-network-wireless-devices-latency-stats with timespan 86400 on a network with active APs that clearly should have stats...

Response: 200  OK

 

 

Copy[
    {
        "serial": "Q3AJ-TC.......",
        "latencyStats": null
    },
    {
        "serial": "Q3AJ-BP.......",
        "latencyStats": null
    },
    {
        "serial": "Q3AJ-YW.......",
        "latencyStats": null
    },
    {
        "serial": "Q3AJ-TD.......",
        "latencyStats": null
    },
    {
        "serial": "Q3AJ-DE.......",
        "latencyStats": null
    }
]

 

 

It looks just like the problem that exists with the getNetworkWirelessDevicesConnectionStats call returning nulls...

 

https://community.meraki.com/t5/Developers-APIs/Has-getNetworkWirelessDevicesConnectionStats-stopped...

 

Note that both calls are requesting wireless stats network-wide, both are returning device IDs ok, but with nulls instead of the appropriate data, imo that suggests something is broken in the v1 API server that both calls rely on.

 

The getNetworkWirelessDevicesConnectionStats call has been broken since 6-7 January, that is over four months now.

 

Latest Meraki support feedback from internal teams is that "this issue is not treated with high priority".

 

Fyi the only workaround I found is to rewrite to use the equivalent v0 API call, but that's not a long term solution and of course it gets messy having to mix v0/v1 APIs in applications

 

Can any of the Meraki people say what expectation customers should have for v1 API calls being fixed?

 

View solution in original post

Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.