-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[receiver/mongodbatlas] Make getProcessDatabaseMeasurementsPage() optional to reduce API calls on Atlas clusters #10569
Comments
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
The mongodbatlas receiver is consistently returning 429 due to too many requests. The reason for this is because it is polling for database stats on each poll, which is extremely expensive and makes an individual API call for every database in an Atlas cluster. The number of databases a user can have on their Atlas cluster is unbounded and the high chance of getting rate limited significantly reduces the effectiveness of this receiver. This will be especially apparent in any production environment.
I would like the collection of per database metrics an optional configuration setting. I believe the collection of database metrics should be disabled by default, due to the performance impact of collecting these metrics.
It looks like this is the line where it is looping through each database to get database metrics. Making this optional would help alleviate the rate limiting.
The text was updated successfully, but these errors were encountered: