[SERVER-55378] Audit logic for the agg stage counters in serverStatus() Created: 19/Mar/21  Updated: 06/Dec/22  Resolved: 20/Apr/21

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

Type: Task Priority: Major - P3
Reporter: Katya Kamenieva Assignee: Backlog - Query Execution
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Query Execution
Participants:

 Description   

Review and document when the counter for each stage is/is not increased.
For example:

  • $match stage with $text will not be counted if there's no text index.
  • $search stage counter will be incremented every time


 Comments   
Comment by David Storch [ 22/Mar/21 ]

kateryna.kamenieva can you clarify what exactly we are auditing? My understanding of the current behavior is that we will count every instance of an agg pipeline stage we see in a query, regardless of whether the query succeeds or fails. This seems like correct (and simple) behavior to me. Are we proposing only bumping the counters of the operation succeeds? Or having some special cases where we don't count queries we receive in certain circumstances?

Also, should this ticket be in the "Needs Scheduling" state so that we look at it up during our triage meeting?

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