[SERVER-82629] Surface metrics that show when change collections are idle Created: 31/Oct/23 Updated: 20/Dec/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Sebastien Mendez |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Execution
|
||||
| Sprint: | QE 2023-12-11 | ||||
| Participants: | |||||
| Description |
|
If a change collection isn't being used for a while, Atlas should be able to decide to turn off change streams for a given tenant. We should surface "last read" date for a change collection on a per-tenant basis. CC milkie@mongodb.com |
| Comments |
| Comment by Sebastien Mendez [ 20/Dec/23 ] |
|
As discussed with kateryna.kamenieva@mongodb.com, I'm moving this ticket to the CLOUDP-99450 project. I'm keeping the assignment, because if needed, it could be carried out by someone from my team.
|
| Comment by Chris Hutchinson [ 17/Nov/23 ] |
| Comment by Eric Milkie [ 31/Oct/23 ] |
|
Note that we wouldn't want to durably store these dates, so it would be okay for this to be "most recent usage as of process start" date. |