FlexMeasures / flexmeasures / 38387024987

87%

push

github

Log who hit a rate limit, and which triggers spent the budget (#2678)

* Log who hit a rate limit, and which triggers spent the budget

A budget is shared by everyone it counts, so a 429 alone does not tell a host which integration used it up.
Each refused request is now logged as a warning, naming the limit and its value, the account and user (or IP address), the endpoint and, for the trigger limit, the asset.
Each counted trigger is logged at debug level, with the same details.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MSo5u94LjgXLeMJ51Pja39
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* Changelog: log who hit a rate limit

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MSo5u94LjgXLeMJ51Pja39
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* Docs: refusal warnings need LOGGING_LEVEL at WARNING or lower, which production servers are not by default

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MSo5u94LjgXLeMJ51Pja39
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* remove extra logging import

Signed-off-by: Nicolas Höning <nicolas@seita.nl>

* restore util function that was deleted in b04bf9f01 (#2679) as we still use it here; also added a light-weight test for it

Signed-off-by: Nicolas Höning <nicolas@seita.nl>

* api/v3_0/tests: restore rate limit plans after tests

Context:
- The module shares account rows, and an unlimited plan leaked into later logging tests.

Change:
- Restore the original plan after each test that assigns a plan to the shared account.

* api/rate-limiting: audit account budget breaches once per window

Context:
- Accounts need a durable signal when their shared API or trigger budget is exhausted.

Change:
- Record one account audit entry per limit window with the plan, effective limit, and elapsed time.
- Keep deduplication in limiter sto... (continued)

72 of 79 new or added lines in 2 files covered. (91.14%)

21490 of 24800 relevant lines covered (86.65%)

0.87 hits per line