[SERVER-70933] Implementation for new aggregation stage Created: 28/Oct/22 Updated: 29/Oct/23 Resolved: 11/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Joshua Lapacik (Inactive) | Assignee: | Jess Balint |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | QO 2022-11-14 | ||||||||
| Participants: | |||||||||
| Description |
|
The implementation for the stub created in https://jira.mongodb.org/browse/SERVER-70932, i.e the read path. It will have two modes of operation
(1) will return a snapshot of the telemetry store at a point in time while (2) will not. Note, we should track and return a "first seen" timestamp for each entry as well as the time that entry was read/scanned. This is particularly important for (2) so that downstream consumers can determine if entries were evicted or not. Both modes should minimize blocking writes.
|
| Comments |
| Comment by Githook User [ 11/Nov/22 ] |
|
Author: {'name': 'Jess Balint', 'email': 'jbalint@gmail.com', 'username': 'jbalint'}Message: |