Slack Thread

• antonio.fuschetto@mongodb.com: Hi! When I run the server tests locally (using `resmoke.oy`), I get the following error:
  ```$ ./buildscripts/resmoke.py run --storageEngine=wiredTiger --storageEngineCacheSizeGB=0.5 --mongodSetParameters='{logComponentVerbosity: {verbosity: 2}}' --jobs=1 --log=file --suite=sharding jstests/sharding/move_primary_basic.js
  No replica set members found yet, Timeout: 1.0s, Topology Description: <TopologyDescription id: 63bd2f1b6630d82ab1370f61, topology_type: ReplicaSetNoPrimary, servers: [<ServerDescription ('pl-0-us-east-1.kewhj.mongodb.net', 1024) server_type: Unknown, rtt: None>, <ServerDescription ('pl-0-us-east-1.kewhj.mongodb.net', 1025) server_type: Unknown, rtt: None>, <ServerDescription ('pl-0-us-east-1.kewhj.mongodb.net', 1026) server_type: Unknown, rtt: None>]>

Internal Metrics Collection Failed – this is a non-issue.
If this message persists, feel free to reach out to #server-dev-platform```
Does it depend on my environment? I upgraded the toolchain recently.

• tausif.rahman@mongodb.com: Hi Antonio, thank you for reaching out! Have you seen this problem before – and are you on a virtual workstation?

You can add `TOOLING_METRICS_OPT_OUT=1` to your environment for now. I’m guessing you are in the `eu-west` region, which doesn’t have access to the VPC endpoint yet. We have <https://jira.mongodb.org/browse/SERVER-71595|SERVER-71595> to address this.

• antonio.fuschetto@mongodb.com: Hi U01HS32GGGH, thanks for replying on this. Yes, it’s on my workstation located in `eu-west` (this was another relevant input for the analysis).