The issue involves data collection from two Cisco Meraki organizations:

While retrieving data through the Meraki API, intermittent HTTP 429 (Too Many Requests) errors are being encountered. Various approaches have already been tested, including simultaneous API calls, sequential polling, and scheduled API requests, but rate-limit errors continue to occur. In most cases, the Org ID 1 is the one affected.

As confirmed by Meraki TAC, the API rate limit is enforced at the organization level and cannot be modified. The current limit is 5 requests per second per organization, with a burst allowance of approximately 10 requests in a short period.

Further analysis indicates that the issue may also be related to the behavior of the standard Zabbix Cisco Meraki template. The out-of-the-box template uses HTTP agent items with direct JSON preprocessing and may not gracefully handle HTTP 429 responses returned by the Meraki API during rate-limiting events.

A support case has been opened with Zabbix Support to obtain guidance on:

Recommended best practices for monitoring multiple Meraki organizations.
Handling Meraki API rate limiting within Zabbix.
Potential template optimizations or modifications to improve resilience against HTTP 429 responses.