Oracle Cloud monitors show "Maximum Rate Exceeded" error
The Maximum Rate Exceeded error occurs in Oracle Cloud and its child monitors when too many APIs are accessed at the same time. This error happens usually in an environment where there are large number of Oracle Cloud child monitors like Instances and Storage.
Reason: In Oracle Cloud, the API rate is very low by default. The default API rate limit is 10 Transactions per Second. When polling happens for more than 10 OCI monitors at the same time, this limit is exceeded and hence you might encounter the Maximum rate exceeded error.
Resolution: Follow the steps given below to avoid this error.
- Increase Rate Limit:
- To increase the rate limit ie. TPS (Transactions per Second), raise a request in the OCI portal.
- In the Support section, you will find an option to raise a request to increase the rate limit.
- It is recommended that you raise a request to increase the rate of the below API to 100 TPS
- /20180401/metrics/actions/summarizeMetricsData
- This is the API that is used the most as it fetches all the performance metrics in all the OCI monitor types.
- Disable fast data collection:
- Go to Admin/Settings -> Performance Polling -> Optimize Data Collection -> Monitor Type -> Oracle Cloud -> Metric Name -> Performance.
- If the 'Enable faster data collection' checkbox is enabled, then disable the same.
- If this option is enabled, then multiple API calls happen parallelly for a single monitor and when multiple monitors are polled at the same time, the rate might exceed and cause error.
- Maintain optimum thread count:
- In Applications Manager if the value of the KeyValueMonitor Thread count is high, then there are more chances of multiple monitors being polled at the same time
- To check this go to Admin/Settings -> Server Settings -> Threads Configuration page.
- In some customer environments, we might have suggested you to increase this thread count to avoid thread blocking in other monitor types.
- In such an environment if you a have large number of OCI monitors, it is recommended to move the OCI monitors to a separate Managed server and maintain optimum thread count.
New to ADSelfService Plus?
Related Articles
APM Monitors in OpManager Plus SAM Bundle
APM Monitors in OpManager Plus With the new device-based licensing model for OpManager plus, you can now add monitors of Applications Manager as devices in OpManager Plus using the SAM bundle. You can allocate devices in the SAM bundle in the form of ...
Instance based license for MSSQL and Oracle Monitors
In a single server, there can be multiple instances of Oracle/MSSQL database. Each instance is counted for licensing in Applications Manager. Example 1: In the above image, you can see that there are 3 instances of MS SQL DBs in a single server, ...
How to resolve the "ORA-01017 : Invalid Username/Password; Logon denied" error in an Oracle monitor
In Applications Manager, users might encounter the following error while attempting to add or monitor the Oracle database. This error indicates an issue with authentication credentials or other related configuration settings. To troubleshoot this ...
How do I monitor Oracle Alert Logs?
Alert Log monitoring in Applications Manager is not enabled by default. Here is how you can enable monitoring of Alert Log statistics: Go to the Admin tab. Click Performance Polling under Discovery and Data Collection. Under Performance Data ...
Troubleshoot - Duplicate APMInsight Monitors
Introduction Duplicate monitors might be created in APMInsight due to various reasons. This article will help you identify and resolve the issue of duplicate monitors. The common causes include: - Changes in monitor configuration. (apminsight.conf ...