[SERVER-71027] Ensure $operationMetrics works correctly in multitenancy mode Created: 02/Nov/22  Updated: 16/Oct/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Janna Golden Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-68975 Use DatabaseName and NamespaceString ... Backlog
depends on SERVER-70826 Have ScopedMetricsCollector support D... Backlog
Assigned Teams:
Service Arch
Participants:

 Description   

Ensure the agg stage $operationMetrics works correctly when running with multitenancySupport.



 Comments   
Comment by Janna Golden [ 02/Nov/22 ]

We'll need to change the MetricsMap on the ResourceConsumption class to store DatabaseName objects as the key rather than strings. We should filter docs being returned by tenantId (perhaps by passing tenantId to ResourceConsumption::getDbMetrics), we'll also need to make sure we correctly serialize the db name in any returned documents.

Generated at Thu Feb 08 06:17:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.