-
-
Notifications
You must be signed in to change notification settings - Fork 216
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
Feature request: MongoDB client instrumentation #2578
Labels
Feature
New feature or request
Comments
That's a great feature request, thanks for reaching out! I'll bring that up for the next planning. |
A rudimentary integration is possible using OpenTelemetry. See the #2634 pull request. It might be possible to improve this further by implementing some custom enrichers in Sentry. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Statement
While Sentry provides low-effort instrumentation of HTTP Client and SQLClient, this does not exist for MongoDB client.
It would be really useful if there was an easy way for developers to get more insight into transaction performance of MongoDB using Sentry.
In the recent release 3.36.0 instrumentation of GraphQL queries was added (#2538).
The original feature request ticket #2449 makes a case to support at least the most popular GraphQL library based on number of installs.
If we compare this with the installation of the MongoDB.Driver package, we can see that MongoDB.Driver is used about 6 times as much, which makes a case for supporting MongoDB.
Ofcourse it is not realistic to expect Sentry to have built-in support for all possible third-party packages on Nuget, but growing this support to include popular choices like MongoDB, Redis, S3 etc. would make Sentry even more attractive.
References
See also:
The text was updated successfully, but these errors were encountered: