Skip to content
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

Closed
sunfranklin opened this issue Jun 2, 2022 · 2 comments

Comments

@sunfranklin
Copy link

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.

@sunfranklin sunfranklin changed the title Make getProcessDatabaseMeasurementsPage() optional to reduce API calls on Atlas clusters [receiver/mongodbatlas] Make getProcessDatabaseMeasurementsPage() optional to reduce API calls on Atlas clusters Jun 2, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Nov 9, 2022

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Nov 9, 2022
@github-actions
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants