[SERVER-80675] Analyze where and how to duplicate metrics returned by commands used for monitoring Created: 01/Sep/23 Updated: 14/Sep/23 Resolved: 14/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Pol Pinol |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Sprint: | Sharding EMEA 2023-09-18 |
| Participants: |
| Description |
|
Information reported by Atlas UI to monitor sharded clusters is retried invoking a set of commands exposed by MongoS and MongoD (see By embedding the router service into MongoD, these commands should be exposed from the main and router ports maintaining the same behavior as compared to having two separate processes. The serverStatus command, for example, retrieves metrics from the ServerStatusSectionRegistry (SERVER-79353) and the MetricTree (SERVER-79352), but others count events by using custom variables. The goal of this ticket is to identify these commands implemented using the custom variable and evaluate a solution to keep separate statistics for router and service. |