[SERVER-58688] Log lines for slow change stream operations should list both original collection and slow collection / oplog Created: 20/Jul/21  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Eric Sommer Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 1
Labels: change-streams-improvements, tscs-ramp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Query Execution
Participants:
Case:

 Description   

Log lines for slow operations normally list the collection on which the slow operation run.  There is one exception: for change stream operations, the log lists the original collection against which the change stream operation was run, even though the slow operation actually read from a different collection - the oplog (as all change stream operations do).

This can be a bit misleading, as the log line makes it look like the operation took a long time to run on the original data collection, even though it didn't run on that collection at all.

Ideally, the logged slow change operations should show both the original collection against which the change stream was run and the collection on which it actually run in practice (oplog).


Generated at Thu Feb 08 05:45:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.