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.

• Okta Rate Limiting
• Okta System Log

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.

If a rate limit violation error occurs, perform the following steps to investigate the usage:

1. Review the backend application to determine the total number of API calls it makes.
2. Identify the specific endpoint where the rate limit violations occur.

Related References

• API rate limits 
• How to Search System Log for Rate Limit Violations, Bursts, and Warnings
• Rate Limit Frequently Asked Questions
• How to Request a Rate Limit Increase