getDeviceAppliancePerformance Returning 204 - No Content

giovanitestoni
Here to help

getDeviceAppliancePerformance Returning 204 - No Content

Hi everyone,

I’m encountering an issue with the getDeviceAppliancePerformance endpoint of the Meraki API. Until last month, it was working perfectly, but now it’s returning the HTTP status code 204 - No Content.

The expected behavior of this endpoint is to return performance metrics for a specific device, but it now returns an empty response.

Has anyone else experienced this issue recently? Was there any update or change to this endpoint that I may have missed?

Any guidance or suggestions would be greatly appreciated!

7 Replies 7
alemabrahao
Kind of a big deal
Kind of a big deal

Can you share your code please?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
giovanitestoni
Here to help

Hi!

 

My code is the same as the documentation:

 

https://developer.cisco.com/meraki/api-v1/get-device-appliance-performance/

 

The script started to return an error because the response needed to be Numerical/Float and None is a String.

 

 

GreenMan
Meraki Employee
Meraki Employee

Generically, this endpoint seems to be working OK for me, through a single call

RaphaelL
Kind of a big deal
Kind of a big deal

You should avoid "device" specific calls and use this one : https://developer.cisco.com/meraki/api-v1/get-organization-summary-top-appliances-by-utilization/  You can use any value for quantity

giovanitestoni
Here to help

With the timespan < 44000 the return is None too.

giovanitestoni
Here to help

I made some tests and the code works when I put the timespan > 44000, normally I use the default value. The default is 30 minutes.

giovanitestoni
Here to help

I opened a case, and support tell me that this issue is known and they are working for a fix.

 

There is no ETA at the moment.

Get notified when there are additional replies to this discussion.