You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
API Manager currently cannot reset the request counters manually after or before the throttle policy limit has been reached within the throttling time window. The throttle policy limit can be reached due to spikes or unintended requests. Hence, API Users should wait until the throttling time period expires to invoke API calls again. In that case, there can be a requirement to allow further usage resuming API consumption for consumers seamlessly.
Solution
The proposed solution involves publishing a separate asynchronous reset event to the current Siddhi stream at the traffic manager. We are planning to use the existing Siddhi event stream process flow with additional changes to support resetting relevant counters. This approach involves changing the current execution plan format and creating a new data publisher to publish the reset event to the Siddhi runtime.
Affected Component
APIM
Version
4.2.0
Implementation
High level design for the proposed solution.
Tasks to be done
Application Level Throttle Policy Reset
Rest API implementation
Notify the reset event to eventhub
Publish the reset event fetched from event hub to Siddhi Stream
Write Siddhi extensions to handle reset event
Frontend Implementation
Unit Testing
Integration Testing
Update APIM docs
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered:
Problem
API Manager currently cannot reset the request counters manually after or before the throttle policy limit has been reached within the throttling time window. The throttle policy limit can be reached due to spikes or unintended requests. Hence, API Users should wait until the throttling time period expires to invoke API calls again. In that case, there can be a requirement to allow further usage resuming API consumption for consumers seamlessly.
Solution
The proposed solution involves publishing a separate asynchronous reset event to the current Siddhi stream at the traffic manager. We are planning to use the existing Siddhi event stream process flow with additional changes to support resetting relevant counters. This approach involves changing the current execution plan format and creating a new data publisher to publish the reset event to the Siddhi runtime.
Affected Component
APIM
Version
4.2.0
Implementation
High level design for the proposed solution.
![image](https://private-user-images.githubusercontent.com/118423471/302362608-d9f5139f-c5a8-4ee7-a7d6-793873840ca7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjI0Nzg4ODUsIm5iZiI6MTcyMjQ3ODU4NSwicGF0aCI6Ii8xMTg0MjM0NzEvMzAyMzYyNjA4LWQ5ZjUxMzlmLWM1YTgtNGVlNy1hN2Q2LTc5Mzg3Mzg0MGNhNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODAxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgwMVQwMjE2MjVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yYTIxNjAyMDI3ZDU0NDNiOWMyNTM0ZGMxNjJiODA5OTQ2NTU4NTcxMjY5NTI2YzA0YmNhYWE3NDkyMDMxMmVjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.0LzQtE5iDM9jyi2qP1jXJrNFvD_beTNy6rYTS_6bNhE)
Tasks to be done
Application Level Throttle Policy Reset
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: