Zenoss Rate Limits
Zenoss / Virtana Service Observability documents no rate limits. Every /v1 API reference page was read — data receiver, event query, event management, model context (entities and maintenance windows), dictionary (metrics, entity fields, event fields), actions, credentials and user management — and none publishes a quota, a throttle threshold, a burst allowance, a rate-limit response header, or a 429 status code. The published status-code tables run 200/400/401/404/409/ 500/501 with no 429 anywhere. The only numeric ceilings Zenoss publishes are on key management (200 keys per API Client, 130 Collection Zone keys per user), which are not request limits.
Zenoss Rate Limits is the rate-limit profile for Zenoss on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers.
The profile also includes response codes documented for throttled, quotaExceeded, and note.
Tagged areas include AIOps, Monitoring, and Observability.
limitremainingresetretryAfter
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.