Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
Catalog and Routing
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.
Attachments
Issue Links
- depends on
-
SERVER-82931 Mark each FTDC collector with a prefix to indicate its type (service, process or host)
-
- Open
-