Skip to content
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

Mongo traces no longer showing #697

Closed
lwakefield opened this issue Sep 26, 2019 · 1 comment · Fixed by #700
Closed

Mongo traces no longer showing #697

lwakefield opened this issue Sep 26, 2019 · 1 comment · Fixed by #700
Labels
bug Something isn't working community integrations
Milestone

Comments

@lwakefield
Copy link

lwakefield commented Sep 26, 2019

Describe the bug

We recently upgraded some mongo dependencies:

FROM: 
    "mongodb": "^2.0.49",
    "mongoose": "^4.13.17",
    "mongoose-deep-populate": "^1.1.0",
TO:
    "mongodb": "^3.3.1",
    "mongoose": "^5.2.13",
    "mongoose-deep-populate": "^3.1.1",

Since that upgrade - mongo traces have stopped showing in APM.

I am testing an upgrade to dd-trace-js in case that fixes the issue. No luck with the upgrade.

Additionally I am in the process of testing the order in which dependecies are loaded to make sure dd-trace-js is still initialized first. It appears that dd-trace-js is still initialized before everything else.

Environment

  • Operation system: Heroku Dyno
  • Node version: 10.x
  • Tracer version: 0.15.3
  • Agent version: Heroku Buildpack
@lwakefield lwakefield added the bug Something isn't working label Sep 26, 2019
@rochdev
Copy link
Member

rochdev commented Sep 27, 2019

It looks like since mongodb 3.3.0 they have merged mongodb-core which is thus no longer a standalone library. Since we instrument mongodb-core which no longer exists, the plugin is never used. We'll need to update the plugin to support the new merged project. If you do not have a strong reason to use >=3.3.0, I would recommend downgrading in the meantime. This should be fixed in the next few days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working community integrations
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants