- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Duplicate client records returned by getOrganizationWirelessDevicesPacketLossByClient
I was doing some testing and notice a problem with one of these new endpoints...
The 'by client' endpoint sometimes returns duplicate client records. I've tried it with/without a band filter, behaviour is similar.
Btw I do not see any duplicates on the 'by device' endpoint.
Without a band filter, there are sometime two or more identical records for the same client.
With band filters and consolidating data for the three bands, the duplication may occur on one, two or all three bands.
This org has > 40,000 clients in the sample period (September 2023), running for each band, over 6,000 network-client records have a least one duplicate in one or more bands, one has 20 in all three bands.
Number of copies per network-client-band, should only be 1 copy per unique network-client-band...
unique network-client-band | copies |
114792 | 1 |
4299 | 2 |
920 | 3 |
188 | 4 |
247 | 5 |
85 | 6 |
28 | 7 |
19 | 8 |
19 | 9 |
20 | 10 |
19 | 11 |
43 | 12 |
56 | 13 |
11 | 14 |
12 | 15 |
18 | 16 |
28 | 17 |
19 | 18 |
14 | 19 |
3 | 20 |
Sample with network and MAC hidden (any given client is on just one network, id-MAC are identical)...
period | id | band | upTotal | upLost | upLost% | downTotal | downLost | downLost% |
2023-09 | k04037a | 2.4 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k04037a | 2.4 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k04037a | 5 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k04037a | 6 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k04037a | 6 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k040e89 | 2.4 | 3036 | 80 | 2.6 | 2855 | 245 | 8.6 |
2023-09 | k040e89 | 2.4 | 3036 | 80 | 2.6 | 2855 | 245 | 8.6 |
2023-09 | k040e89 | 5 | 309095 | 2473 | 0.8 | 595930 | 7173 | 1.2 |
2023-09 | k040e89 | 6 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k040e89 | 6 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k046f49 | 2.4 | 22 | 0 | 0 | 12 | 0 | 0 |
2023-09 | k046f49 | 5 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k046f49 | 6 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k046f49 | 6 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k0488f2 | 2.4 | 994 | 31 | 3.1 | 860 | 59 | 6.9 |
2023-09 | k0488f2 | 2.4 | 994 | 31 | 3.1 | 860 | 59 | 6.9 |
2023-09 | k0488f2 | 5 | 20936 | 42 | 0.2 | 28124 | 2166 | 7.7 |
2023-09 | k0488f2 | 6 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k0488f2 | 6 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k077886 | 2.4 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k077886 | 5 | 3651 | 61 | 1.7 | 11041 | 1661 | 15 |
2023-09 | k077886 | 6 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k077886 | 6 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k0c5216 | 2.4 | 51 | 0 | 0 | 33 | 0 | 0 |
2023-09 | k0c5216 | 5 | 0 | 0 | 0 | 0 | 0 | 0 |
2023-09 | k0c5216 | 6 | 0 | 0 | 0 | 0 | 0 | 0 |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You should raise a case with Meraki Support for this, I think - if you didn't already.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I already have several cases open on other API issues, some open for a long time now.
As this endpoint is only just GA after a pretty short beta period, I would like Meraki to own it and look at the problem without me needing to open yet another case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello! 👋 My team owns this API and are working on additional endpoints that serve metrics per-client. Filing a support case with specific examples regarding the network(s) where this occurs and the clients that are duplicated would be very helpful for us. 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I opened case 10959729 it identifies an org where the problem occurs and also IDs of one of the networks/clients showing duplicates (there are many more).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Meraki support claim that it is correct for multiple identical client records to be returned and want to close the case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm just getting the runaround from support now, it is exactly why I did not want to open a case!
