[SERVER-75912] Telemetry on view queries should store the query shape without view resolution Created: 10/Apr/23  Updated: 14/Sep/23  Resolved: 22/May/23

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

Type: Task Priority: Major - P3
Reporter: Will Buerger Assignee: Backlog - Query Integration
Resolution: Duplicate Votes: 0
Labels: read-only-views
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-85099 Tracking: Milestone 1 Closed
is depended on by SERVER-85105 Tracking: PM-2885 Milestone 0 Closed
Duplicate
duplicates SERVER-71987 Add collection type to telemetry key Closed
Related
related to SERVER-77262 Track queries on non-existent collect... Closed
related to SERVER-77389 Complete TODO listed in SERVER-75912 Closed
related to SERVER-78072 Complete TODO listed in SERVER-75912 Closed
is related to SERVER-71987 Add collection type to telemetry key Closed
Assigned Teams:
Query Integration
Participants:

 Description   

In the case we're running a query against a view, telemetry should be collected with a telemetry key that reflects the unresolved view query shape, not with the resolved pipeline on the underlying collection. We should add tests to make sure that's happening properly in each of the mongod and mongos find and agg cases.



 Comments   
Comment by Charlie Swanson [ 22/May/23 ]

Spoke with jess.balint@mongodb.com and we will solve this in SERVER-71987 so I'll close this out.

Comment by Charlie Swanson [ 26/Apr/23 ]

jbalint@gmail.com was this done/tested as part of SERVER-71987? Any code/tests we could re-use there?

Generated at Thu Feb 08 06:31:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.