|
In the context of PM-635, the Full-Time Diagnostics Capture (FTDC) machinery needs to be adapted to produce performance statistics for both the embedded router and shard/config server for internal usage in the same FTDC data file.
As a first step, we will need to extend the information reported in the local FTDC data file depending of the type of information given, using a prefix.
The different types that the collector can represent are the same provided by the investigation at SERVER-79243: host, process and services. That is:
- host
- process
- service - shard
- service - router
- service - config
The goal of this ticket is to mark each FTDC collector with a prefix that indicated the corresponding type.
An example of current implementation:
{
|
"start" : Date_t,
|
"collector1" : {
|
"start" : Date_t,
|
"data" : { ... }
|
"end" : Date_t,
|
},
|
"collector2" : { ... },
|
...,
|
"end" : Date_t,
|
}
|
Goal of this ticket:
{
|
"start" : Date_t,
|
"shard" : { "collector1" : { ... } },
|
"shard" : { "collector2" : { ... } },
|
"process" : { "collector3" : { ... } },
|
"process" : { "collector4" : { ... } },
|
...,
|
"end" : Date_t,
|
}
|
|