-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
165
- depends on
-
SERVER-76597 Reported size of TelemetryMetrics is too small
- Closed
-
SERVER-76919 add gen command fields to query stats key
- Closed
-
SERVER-77262 Track queries on non-existent collections in query stats
- Closed
-
SERVER-71987 Add collection type to telemetry key
- Closed
-
SERVER-75597 Investigate if "crs" is being left off of $geometry telemetry (in $geoWithin and friends)
- Closed
-
SERVER-75609 Fail more gracefully if computing telemetry key or storing telemetry fails
- Closed
-
SERVER-75912 Telemetry on view queries should store the query shape without view resolution
- Closed
-
SERVER-76329 Use representative query shape in telemetry store (find command)
- Closed
-
SERVER-76427 Rename $telemetry to $queryStats
- Closed
-
SERVER-76529 Separate execution time metric into two: one for time to first batch and one for overall time
- Closed
-
SERVER-76531 Test that mongos does not collect telemetry for queryable encryption collections
- Closed
-
SERVER-76553 Shapify readConcern's "afterClusterTime" and ensure we only use client-provided read/write concern values
- Closed
-
SERVER-77179 Update $queryStats parameters
- Closed
-
SERVER-80878 query stats store size serverStatus metric can go below 0
- Closed
-
SERVER-85105 Tracking: PM-2885 Milestone 0
- Closed
-
SERVER-79794 Add unit test to see if 16MB >= query shape triggers failure
- Closed
-
SERVER-76083 Enable more tests on the telemetry variants
- Closed
-
SERVER-77190 Include the whole client metadata in telemetry key, not just appName
- Closed
- is depended on by
-
SERVER-85075 Tracking: Milestone 2
- Closed
- is related to
-
SERVER-85075 Tracking: Milestone 2
- Closed
- related to
-
SERVER-77879 Temporarily raise frequency of query stats builders and their baselines
- Closed
-
SERVER-85105 Tracking: PM-2885 Milestone 0
- Closed