[DOCS-16384] [Server] Investigate changes in SERVER-66018: Expose metrics for readPreference usage Created: 15/Sep/23  Updated: 13/Nov/23  Resolved: 09/Nov/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 7.2.0-rc0, 6.0.11, 7.0.3, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Alison Huh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-66018 Expose metrics for readPreference usage Closed
URL(s): https://www.mongodb.com/docs/manual/reference/command/serverStatus/
Participants:
Days since reply: 20 weeks, 5 days ago

 Description   
Original Downstream Change Summary

serverStatus output now exposes metrics about readPreference. See this document for details about what is exposed: https://docs.google.com/document/d/1GZK3Izg3PBjtjCv1aiptuHQzudHMZlxnO5IdtDBUVgc/edit#heading=h.jmjxxubeuhdo

Description of Linked Ticket

Goal / Product Question:

Our recommended topology is a replica set with three nodes for high availability. However, some customers are questioning the cost associated with running all three nodes, where they claim reads & writes only happen on their primary.

We offer the ability to redirect reads to a secondary node. We believe there is a population of customers who use secondary reads, but we never had a good way to identify them. Exposing a metric to identify if a secondary node has served reads will help identify these customers who specifically directed reads to a secondary node.

 

Must have: 

-Number of clusters with secondary reads

-Distribution of readPreference options (e.g. secondary, secondaryPreferred, primary)  

 

Nice to Have:

-Hedge Reads 

-Mirror Reads

-Number of clusters with reads with multiple read preferences


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