This is a feature request (not a bug) to enhance FTDC by allowing users to disable the collection of specific groups of metrics.

Currently, FTDC collects a wide array of metrics including systemMetrics, which may contain data not always needed (e.g., disk stats from mount points that are irrelevant to the workload). This can generate unnecessary overhead or clutter when analyzing diagnostic data.

Proposed Enhancement:{}

Introduce support in FTDC for selectively disabling or adjusting the collection interval of particular groups of metrics, such as:

• systemMetrics

• serverStatus.connections

• Other major metric groups (as applicable)

This filtering should ideally support:

• Disabling collection for a whole group (e.g., systemMetrics)

• Optionally: Changing the collection interval for specific groups

Example Use Case:{}

A user may not want to collect disk statistics from certain mount points (e.g., ephemeral or backup drives), and would prefer to disable this group entirely to reduce storage, analysis noise, or system impact.

Sample Metrics (to illustrate the current output):

systemMetrics.disks.sdk.read_time_ms;3812559;...
systemMetrics.disks.sdk.writes;299070;...
systemMetrics.disks.sdk.writes_merged;3663;...
systemMetrics.disks.sdk.write_sectors;196491030;...
serverStatus.connections.current;21278;...
serverStatus.connections.available;29922;...
serverStatus.connections.totalCreated;6242624;...

Motivation:{}

• Reduce data collection/storage footprint

• Focus only on relevant metrics

• Minimize noise during diagnostics and analysis

• Improve customization for performance-sensitive deployments

Acceptance Criteria:{}

• Option exists (e.g., via config or command-line flag) to disable collection of specific metric groups

• Documentation updated to reflect new configuration capability

• FTDC output respects group disabling (no partial data)

• Optional: Allow adjusting collection intervals per metric group