[SERVER-80208] Explore how to leverage resmoke per-test OTEL data Created: 17/Aug/23 Updated: 11/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Steve Gross | Assignee: | Alex Neben |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Build and Correctness OnDeck |
| Participants: |
| Description |
|
Now that resmoke is collecting fine-granularity test OTEL data (dashboard: https://ui.honeycomb.io/mongodb-4b/environments/production/board/3bATQLb38bh/Server-CI), we should spend some time figuring out how useful it is! For instance, we could identify top culprits and work with fellow engineers to address them. |