cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5368
Views
5
Helpful
14
Replies

getNetworkClientsApplicationUsage returns 400!

I'm using getNetworkClients to get the client list, then I use their IDs with getNetworkClientsApplicationUsage to their usage.

Unfortunately, a lot of times I get an error:

Message:{"errors":["One or more clients were not found"]}

I found that the "problematic" devices are Cisco devices, especially "Cisco Meraki".

When I remove from the client list all the devices with manufacturer starts with "Cisco", I don't get this error anymore.

a. Is this familiar?

b. Is there any official way to use the endpoint getNetworkClientsApplicationUsage?

14 Replies 14

Raphael_L
Meraki Community All-Star
Meraki Community All-Star

You shouldn't have Cisco Meraki devices listed in your Network Clients unless they are from a different dashboard Network.

The main issue is why do I get the Cisco devices in the list, while I cannot get info about them in the application endpoint or the usage history endpoint.

Or at least if those endpoint can return the list of the problematic clients I can remove them from the request and send new request.

Philip D'Ath
Meraki Community All-Star
Meraki Community All-Star

Devices with very low usage may not show up as having usage int he API. This is expected behaviour.

I don't care if a device usage show or not. The main problem is that in this case I get 400 and don't get usage of any client!! This is definitely not expected behaviour.

If only there was a detail within the error which clients were not found, I could remove them from the list and request the usage again.

obrigg
Meraki Employee All-Star
Meraki Employee All-Star

Yaakov, did you open a support case about this problem?

Yes, I did.

But like my previous case, they ask me a lot of questions, but don't provide answers.

Can you share the case number? Or a specific API request that would result in a 400 error, so I can take a look.

Case 13304304

I use https://api.meraki.com:443/api/v1/networks/L_xxxx/clients to get the client list.

Then I take their IDs (for example: k09fefe,k09fe1e,k09fe1f,k09fe20,k09fe21,k09fe32) .

Then I use https://api.meraki.com:443/api/v1/networks/L_xxxx/clients/applicationUsage?t0=1753172549&t1=1753173549&clients=k09fefe,k09fe1e,k09fe1f,k09fe20,k09fe21,k09fe32 to get their usage.

The last call returns with 400 and the error message "One or more clients were not found"

I see. Assuming you’re using the same timespan, maybe one of these clients had no traffic during that time.

If you’re listing all clients, would it make more sense to use getNetworkTraffic?

We need the clients and their usage.

How getNetworkTraffic can help us? It just tell me how many client used an application, but don't give me the client list.

The problem I found is a bug in Meraki, and it should be fix. Or at least to give instruction how to use the endpoints without getting error code 400.

The API call you are trying to make would return aggregated information, I don’t see much difference.
Can you perhaps explain the use-case, the data you’re trying to obtain, and how it would be used?

I would like to get as much as we can information about the clients, and look for correlation between client activity and network issues.

For that I need an API with the client usage and activity. The list of application and their usage are not relevant for my case.

So is https://developer.cisco.com/meraki/api-v1/get-network-clients-usage-histories/ the more relevant operation to your use case?

1. I use both operations: getNetworkClientsUsageHistories and getNetworkClientsApplicationUsage.

2. getNetworkClientsUsageHistories also has the same problem with the same Cisco clients.

It happened when I used timespan=1000 and when I used timespan=7200.

In the case I opened, I put all the needed information (net ID, client IDs), but I got strange responses from the support team.

As far as I understand, there is a bug in those 2 endpoints. There are 2 options to fix it:

1. Remove the problematic devices from the client list of getNetworkClients.

2. Or ignore the problematic clients when responding to getNetworkClientsUsageHistories or getNetworkClientsApplicationUsage.

If the Meraki R&D team has a better solution - welcome!

p.s. I found a real bug. Why does no one give me kudos?