Skip to content

Use direct_connection in mongodb discovery #6042

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

Merged
merged 1 commit into from
Mar 27, 2025

Conversation

dmitryax
Copy link
Contributor

With disabled direct connection, the mongodb receiver tries to discover other endpoints by itself. Given that the discovery receiver covers all endpoints on every node, such configuration can end up in cross-nodes scraping, metric duplication and failures. The mongodb receiver 0.121.0 was also changed to actively look for secondary hosts which may result in collector stuck on startup when it cannot reach other endpoints.

With disabled direct connection, the mongodb receiver tries to discover other endpoints by itself. Given that the discovery receiver covers all endpoints on every node, such configuration can end up in cross-nodes scraping, metric duplication and failures. The mongodb receiver 0.121.0 was also changed to actively look for secondary hosts which may result in collector stuck on startup when it cannot reach other endpoints.
@dmitryax dmitryax requested review from a team as code owners March 27, 2025 16:21
@dmitryax dmitryax merged commit 950ace0 into main Mar 27, 2025
254 checks passed
@dmitryax dmitryax deleted the use-direct-connection-mongodb-discovery branch March 27, 2025 17:10
@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants