-
Feature Request
-
Resolution: Unresolved
-
Minor
-
None
-
2.10 GA
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
- Proposed Title of This Feature Request
-
- Enhanced Rate Limiting Monitoring and Granular Control in 3scale
- Problem/Feature Description
-
- The customer is currently operating 3scale version 2.10. To manage the high volume of requests, they have implemented rate limiting but face challenges in verifying its effectiveness. The existing monitoring capabilities in version 2.10 are limited to a minimum of one hour intervals, which restricts the ability to verify if rate limits set per minute are functioning correctly.
- Rate limits can be set per minute, but there are insufficient monitoring tools to verify that these settings are functioning as intended. For example, a general API has a rate limit of 2700 requests per minute. However, based on other log information (such as DB logs or logged request counts from 3scale), it appears that up to 4000 requests or more are being processed per minute. This discrepancy suggests that the rate limit is not being applied correctly, but there is no way to verify this within 3scale itself.
- The customer requests that this feature be implemented in the latest version of 3scale to enhance rate limiting monitoring and ensure the proper application of rate limits.
- Why Does the Customer Need This?
-
- Monitoring rate limits at a one-minute interval would make it easier to verify that rate limiting is functioning correctly and to demonstrate to customers that the issue is not with 3scale.
- List Any Affected Packages or Components
-
- 3scale API Management
- References
-
- Current Version: 3scale 2.10
- Observed Issue: Inconsistent application or inadequate monitoring of rate limits.
- Related Documentation: Red Hat Solution for Rate Limiting
