System Log Count Does Not Match Rate Limit Threshold
Last Updated:
Administration
Okta Identity Engine
Overview
This article explains why the total event count or graph in the System Log may not align with specific rate limit thresholds. For example, the System Log might display 330 events per minute while a rate limit violation occurs at a threshold of 600 requests per minute.
Applies To
- Okta Rate Limiting
- Okta System Log
Cause
The System Log does not register every individual Application Programming Interface (API) call made to the system. A rate limit violation indicates the total requests exceeded the allowed limit, even if those specific calls are not all visible in the Okta System Log.
Solution
If a rate limit violation error occurs, perform the following steps to investigate the usage:
- Review the backend application to determine the total number of API calls it makes.
- Identify the specific endpoint where the rate limit violations occur.
