apank

@sattarab - I'm having the same issue with mongoose after updating dd-trace. For me if I use dd-trace 2.2.0 all my mongo traces are logged; but if I upgrade any...

> @rochdev It works when I downgrade it to 2.2 so I am going to do that for now. @apank thankyou so much for the suggestion np, it's very frustrating...

I'm using mongoose v5.13.14 which use mongodb v3.7.3 I tested the latest version of dd-trace (2.10.0) - it didn't capture any of the mongo traces at all :(

I use mongoose On Thu, Jun 16, 2022, 11:07 AM sattarab ***@***.***> wrote: > @apank have you tried it with mongodb 4.7.0? > > — > Reply to this email...

@ahmedelshenawy25 every new release they have breaks things and introduces new bugs; I've been stuck on 2.2.0 because that is the only latest version that supports mongo properly

@avivshafir @sattarab @guspio @ondrejnebesky @nicolas-vivot Great news! A few weeks ago I was able to try @rochdev's suggestion above and everything has been working as expected for me in v3.9.3...

@AdriaanJoubert did you make sure you switched to this branch and you weren't on master. It's working for me.

This is because you aren't supposed to run tests on your live db; I answered a similar question [here](https://github.com/hagopj13/node-express-boilerplate/issues/294#issuecomment-2272780172)

> I was able to fix it by following [this](https://stackoverflow.com/questions/65305856/no-write-concern-mode-named-majority-found-in-replica-set-configuration-err) . > > Looks like the [.env.example](https://github.com/hagopj13/node-express-boilerplate/blob/master/.env.example) needs the `MONGODB_URL` to be updated like the url in .env.example is referencing...