[SERVER-41106] Support OpenTracing in MongoD and MongoS Created: 13/May/19 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | John Festa | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | sa-remove-fv-backlog-22 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
I'm working with a customer who is requesting OpenTracing support in the Mongo Go Driver as well as the core server (mongod, mongos). The customer is looking to collect metrics, many of which are collected in the diagnostics folder, but correlated with individual requests. I see there was a previously created Jira to add OpenTracing to the Go Driver which was resolved "wont fix" with an indication the functionality can be built on top of the command monitoring API. https://jira.mongodb.org/browse/GODRIVER-739 Please let us know if OpenTracing support is something that can be considered for acceptance into the engineering stream and if not, an alternative mechanism to achieve some of the same benefits. Reference:
|
| Comments |
| Comment by Albert Wong (Inactive) [ 30/Apr/21 ] |
| Comment by Albert Wong (Inactive) [ 30/Apr/21 ] |
|
I have a potential customer that is interested in opentracing for the go drivers. |
| Comment by David Bartley [ 12/Oct/20 ] |
|
I'd also be interesting in seeing support for this. If we can agree upon a framework/proposal we could look into doing the work to get it supported. |