Requests being sent to compass.mongodb.com

Sh_Ag · 2024-12-06T20:39:34.180Z

We are observing traffic being sent to compass.mongodb.com in our tcpdump analysis, even though none of our setup is configured to connect to compass.mongodb.com. Could you help us understand why this is happening?

We have tried disabling telemetry in MongoDB using both mongosh commands (disableTelemetry() and db.adminCommand({ setParameter: 1, diagnosticDataCollectionEnabled: false })). After this, we monitored the network traffic using tcpdump and noticed that requests to endpoints like vortex.data.microsoft.com and api.segment.io have stopped, which aligns with the expected behavior.

However, we still see requests being sent to compass.mongodb.com. Could you help me understand why this traffic persists even after disabling telemetry? Is there any additional configuration needed to stop this specific traffic? Or is this related to another feature or service of MongoDB?

Thank you!

Massimiliano_Marcon · 2024-12-09T09:23:32.585Z

Requests sent to compass.mongodb.com are likely to check for updates.

Note that you can configure how Compass behaves quite granularly with a configuration file: https://www.mongodb.com/docs/compass/current/settings/config-file/

Sh_Ag · 2024-12-10T13:38:32.537Z

I forgot to mention that we’re using the MongoDB Linux Docker image, which, as far as I know, doesn’t include MongoDB Compass. Therefore, it shouldn’t be checking for any updates. Additionally, we don’t have MongoDB Compass installed in our environment. Can you think of any other reasons why it might be reaching out to compass.mongodb.com? I appreciate your help in looking into this issue.

Chris_Brown · 2025-04-24T06:44:45.200Z

It turns out that the DNS requests to compass.mongodb.com are coming from the MongoDB Snippets feature (experimental?). To stop the flood of DNS requests on a system that isn’t connected to the normal internet (so the requests can never succeed), you can turn off the Snippets feature using mongosh eval commands, and I think through a config file as well.

mongosh --nodb --eval 'config.set("snippetAutoload",false)'
mongosh --nodb --eval 'config.set("snippetIndexSourceURLs","")'