Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-82931

Tag each FTDC collector with the proper role category

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2024-02-19, CAR Team 2024-03-04

      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 role of information given.

      The different types that the collector can represent are aligned with the ClusterRole, that is,

      • ClusterRole::None (the collector is not based on a service)
      • ClusterRole::ShardService
      • ClusterRole::RouterService

      The goal of this ticket is to mark each FTDC collector with a role that indicated the corresponding category.

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: