[DOCS-15985] [SERVER] Investigate changes in SERVER-69954: ShardingDataTransformCumulativeMetrics Does Not Report Oldest Operation's Elapsed Time Created: 24/Mar/23  Updated: 12/Dec/23  Resolved: 19/Sep/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Joseph Dougherty
Resolution: Fixed Votes: 0
Labels: quick-win, server-docs-bug-bash, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-69954 ShardingDataTransformCumulativeMetric... Backlog
Participants:
Days since reply: 45 weeks, 5 days ago

 Description   
Original Downstream Change Summary

Please remove any mentions of totalOperationTimeElapsedMillis due to the work outlined in SERVER-69954. Removing the mention will make docs more accurate.

Description of Linked Ticket

We currently document a serverStatus field shardingStatistics.resharding.totalOperationTimeElapsedMillis, however this field was never actually reported by the old metrics implementation as of 6.0 and is also not reported by the new implementation which we started using in 6.1.

The oldest running resharding operation's elapsed time in milliseconds should be reported in the output of serverStatus as shardingStatistics.resharding.oldestActive.totalOperationTimeElapsedMillis.

Consider also adding a counter for the elapsed time for the most recent successful operation, to ease tracking resharding performance in atlas based on historical serverStatus data.


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