PLAN_008 Logging and monitoring of rate limit violations
Description​
This test verifies that the rate limiting mechanism logs and monitors rate limit violations accurately.
System requirements​
There are no minimum software and hardware requirements to run this test.
Preconditions​
- The entire system (including the reverse proxy, REST API, and all upstream services) is deployed, operational, and accessible online.
- All communications with the REST API are conducted over HTTPS, either through a reverse proxy server or directly with the hosting server.
- Rate limit configured (any configuration for testing).
Input data​
No specific data is needed to perform this test.
Steps​
- Send requests to the API to exceed the configured rate limit.
- Check the log files or monitoring system for entries related to rate limit violations.
- Verify the accuracy of the log entries (timestamp, user information, endpoint accessed, number of requests).
Expected outcome​
- Rate limit violations are logged accurately with appropriate details.
- Monitoring system reflects the rate limit violations correctly for analysis.
Verifies software requirements​
- SWR-003
Risk control for​
- Supporting troubleshooting and analysis of user behaviors.
Signature meaning
The signatures for the approval process of this document can be found in the verified commits at the repository for the QMS. As a reference, the team members who are expected to participate in this document and their roles in the approval process, as defined in Annex I Responsibility Matrix of the GP-001, are:
- Tester: JD-017, JD-009, JD-004
- Approver: JD-005