Werk #20155: Fix wrong bandwidth usage for Cisco Meraki appliance uplinks
| Component | Checks & agents | ||||
| Title | Fix wrong bandwidth usage for Cisco Meraki appliance uplinks | ||||
| Date | Jul 8, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
Problem description
Previously, the bandwidth usage (sent/received) shown by the Uplink service for Cisco Meraki appliances could be wrong: in organizations with more than one appliance sharing the same interface name (e.g. "wan1"), every affected device ended up reporting whichever device's usage data happened to be fetched last, instead of its own. This has been fixed.
Technical background
The special agent queried the organization-wide uplink usage endpoint once per appliance device instead of once per organization, and grouped the result by interface name alone, discarding which device it actually belonged to. Besides causing the wrong values to be mixed up between devices, this also meant the same organization-wide data was needlessly refetched once for every appliance, unnecessarily increasing special agent runtime for organizations with many appliances.
As a side effect, a device/interface that has no usage entry of its own in the API response will now correctly show no bandwidth data instead of another device's numbers.