-
Notifications
You must be signed in to change notification settings - Fork 97
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
Enhanced database reporting for mongoose not working #1382
Comments
@bcoe any news on that ? Is there anything I can do to help you with that? |
@gilles-yvetot unfortunately we don't currently have someone working on this bug. We make a best effort to address bugs within 180 days, so I'm hopeful this will be fixed in the not too distant future. |
Hi @VikramTiwari, which version of mongoose are you using? Unfortunately only mongoose versions 4 - 5 are supported and version 6 is not supported. Support for version 6 is tracked by #1401. |
Hey @gkf We were using mongoose v4 and it wasn't working. Since then we have migrated to mongoose v6 and we are now using open telemetry for capturing and pushing to cloud trace. Sorry about not being able to help here anymore. |
…1382) * chore: Enable Size-Label bot in all googleapis NodeJs repositories Auto-label T-shirt size indicator should be assigned on every new pull request in all googleapis NodeJs repositories * Remove product Remove product since it is by default true Source-Link: googleapis/synthtool@f1562fa Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:bb4d47d0e770abad62699a4664ce6b9ff1629d50c276a6c75860a6a1853dd19b
…1382) (#1431) * chore: Enable Size-Label bot in all googleapis NodeJs repositories Auto-label T-shirt size indicator should be assigned on every new pull request in all googleapis NodeJs repositories * Remove product Remove product since it is by default true Source-Link: googleapis/synthtool@f1562fa Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:bb4d47d0e770abad62699a4664ce6b9ff1629d50c276a6c75860a6a1853dd19b
Closing this out - people who need improved Mongoose telemetry should consider using OTel instead. |
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is this a client library issue or a product issue?
Client library
Did someone already solve this?
No
Do you have a support contract?
No
Environment details
@google-cloud/trace-agent
version: 5.1.5Steps to reproduce
Since I don't see an open issue about mongoose tracking, I am assuming this is something to do with my setup.
Sample:
Here the
User
is coming from thedata-models
package. I can see the request trace in cloud trace but I don't see database spans along with the API.Tracer config:
Any reason this setup might not work as expected?
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
The text was updated successfully, but these errors were encountered: