I'm trying to get network client events through the dashboard api. Most of the time, the request returns a 502 response after waiting around 60 seconds. Other times, it returns the response in around 1 second. I've tried with different values of "perPage" parameter and the result is the same.
Anyone having a similar issue?
I tested this on the following shards, with tries over about 15 minutes just in case:
n205 (502 - bad gateway repeatedly)
n218 (502 - bad gateway repeatedly)
On the 502 shards, getOrganizationNetworks and getNetworkClients work just fine. No issues at all.
But getNetworkClientEvents timed out over multiple tries. Attempts were between 0255 - 0310 UTC.
Can confirm we started seeing these errors on shard n185 today during a deployment.
We started receiving HTTP 502 errors beginning at UTC 2020-01-29T23:52:36.8973977Z.
Further attempts started working around 2020-01-30T06:29:40.0682225Z UTC - so it would have been fixed sometime between those two times.
Hope this helps - I've also logged a case.
Im having the same issue when using getNetworkClientTrafficHistory
some of the clients show up on the Meraki dashboard with traffic. However, when trying to get the data, I get "502 bad gateway".
Note that this works for most clients.
Same for me since today I m getting lot's of 502 errors. I never had those before, when I run the program again, most of the time they disappear but it's ennoying.
Sorry its been a while but I hadn't seen the messages here. This is my case number:
It seems that this endpoint might have these issues by design, and it will be deprecated in favor of "network events" endpoint.
hi. I managed to work around this by using the startingAfter parameter (although documentation says that client should not use this). It seems that if I don't do it, Meraki will try to do a full extract. Some of the clients with highest traffic causes it to crash