[SERVER-82932] Adapt t2 to recognize metric categorization in collectors’ names Created: 08/Nov/23  Updated: 05/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Pol Pinol Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: pm-635-milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-82931 Mark each FTDC collector with a prefi... Open
Assigned Teams:
Catalog and Routing
Participants:

 Description   

The `t2` tool needs to be adapted to be able to graphically represent the categorization introduced by SERVER-82931.

The current implementation of the BSON object to use for `t2` is:

{
   "start" : Date_t,
   "collector1" : {         
      "start" : Date_t, 
      "data" : { ... }  
      "end" : Date_t,
   },
   "collector2" : { ... },
   ...,
   "end" : Date_t,
}

After SERVER-82931, each collector's name has a prefix representing a categorization (i.e., host, process, or shard) as follows:

{
   "start" : Date_t,
   "shard" : { "collector1" : { ... } },
   "shard" : { "collector2" : { ... } },
   "process" : { "collector3" : { ... } },
   "process" : { "collector4" : { ... } },
   ...,
   "end" : Date_t,
}

The objective of this ticket is to make `t2` understand the metric categorization and group them correctly.


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