-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
Fully Compatible
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
I found that these metrics were under a top-level section of serverStatus like this:
"extension.vectorSearch" : { "legacyVectorSearchUsed" : NumberLong(0), "extensionVectorSearchUsed" : NumberLong(0), "onViewKickbackRetries" : NumberLong(0), "inSubpipelineKickbackRetries" : NumberLong(0) }
I think we intended for them to be nested - and in SERVER-115695 we added this section under the top-level 'metrics':
"extension": { "totalAggStageExecMicros": NumberLong(0); }
I think taken together we should move these metrics and have it look like:
"extension": { "totalAggStageExecMicros": NumberLong(0); // Metrics coming in SERVER-115696 "extensionSuccesses": NumberLong(0); "extensionFailures": NumberLong(0); // These metrics: "vectorSearch" : { "legacyVectorSearchUsed" : NumberLong(0), "extensionVectorSearchUsed" : NumberLong(0), "onViewKickbackRetries" : NumberLong(0), "inSubpipelineKickbackRetries" : NumberLong(0) }
- is depended on by
-
COMPASS-10283 Investigate changes in SERVER-117216: Move extension.vectorSearch metrics near other extension metrics
-
- Needs Triage
-
- is related to
-
SERVER-115695 Add metric tracking time spent in extension's getNext() execution
-
- Closed
-
-
SERVER-115696 Add error counter metrics for the extensions API
-
- Closed
-