Uploaded image for project: 'MongoDB Shell'
  1. MongoDB Shell
  2. MONGOSH-1253

Update telemetry client config to make it less intrusive for cli users

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 1.5.1
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • 1
    • Not Needed
    • Iteration Dolphin

      Currently when sending telemetry to the server, telemetry client will retry telemetry flushing attempt up to 3 times with no timeout for the outgoing request, which might lead to very big timeouts in some certain actions happening in mongosh, for example trying to exit with a flush attempts failing with a timeout (8 minutes in one reported case).

      {“t”:{“$date”:“2022-06-14T01:31:15.265Z”},“s”:“I”,“c”:“MONGOSH”,“id”:1000000011,“ctx”:“shell-api”,“msg”:“Performed API call”,“attr”:{“method”:“countDocuments”,“class”:“Collection”,“db”:“jhotel”,“coll”:“hotelInfo”,“arguments”:{“options”:{}}}}
      {“t”:{“$date”:“2022-06-14T01:39:46.049Z”},“s”:“I”,“c”:“MONGOSH”,“id”:1000000045,“ctx”:“analytics”,“msg”:“Flushed outstanding data”,“attr”:{“flushError”:“connect ETIMEDOUT",“flushDuration”:510755}}

      We want to provide a default configuration for the telemetry that will introduce a request timeout of 1 second and disable the retries completely (see thread for some additional context)

            sergey.petushkov@mongodb.com Sergey Petushkov
            sergey.petushkov@mongodb.com Sergey Petushkov
            0 Vote for this issue
            1 Start watching this issue


                Error rendering 'slack.nextup.jira:slack-integration-plus'. Please contact your Jira administrators.