[DOCS-16536] [SERVER] Investigate changes in SERVER-81988: Add optimizer metrics to curOp Created: 12/Dec/23  Updated: 22/Jan/24

Status: Backlog
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

Type: Task Priority: Minor - P4
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: backlog, feature
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-81988 Add optimizer metrics to curOp Closed
URL(s): https://www.mongodb.com/docs/v7.0/tutorial/manage-the-database-profiler
https://www.mongodb.com/docs/v7.0/reference/method/db.currentOp
https://www.mongodb.com/docs/v7.0/reference/command/currentOp
Participants:
Days since reply: 8 weeks, 2 days ago
Story Points: 2

 Description   
Original Downstream Change Summary

Added 2 new fields to slow query logs and profile:
estimatedCost and estimatedCardinality

Description of Linked Ticket

Class curOp contains data specific for the operation and will add estimatedCost, estimatedCardinality, and the query key (as it is defined in the map - see references). curOp already contains information about whether the plan used a collection scan, as well as executionTime and optimizationTime. This will satisfy the goals form the scope to add the data for the system.profile and explain output.


Generated at Thu Feb 08 08:15:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.