We need to enable TSDB indexing for the system integration's metric streams to reduce storage costs. This should be done in 3 broad phases:

• Update mappings to specify dimensions
• Update mappings to specify metric types
• Flip the toggle to enable TSDB indexing mode, update constraint.kibana.version to 8.8

You can find related issues and examples for other integrations in #5233

Current PRs:

• beta release PR - [System] Enable tsdb by default for beta testing for all but core, network and process data_streams #6427
• metric_type - add missing metadata - [System] Add missing metric_type metadata #6395
• dimensions network data_stream: [System] [Network] Add dimensions and clean up duplicated fields definition #6405
• dimensions for add data_sreams, except core, network, process - [System] Add dimensions to system package metrics data_streams only, except core data_streams #6118
• dimensions process data_stream: [System][Process] Add dimensions metadata; remove duplicated fields #6407
• core dimensions - [System][Core] Add dimensions for the core data_stream #6454
• enable tsdb on network - [System][Network] Enable TSDB for network data_stream #6469
• process metric_type [System][Process] Add metric_type metadata for the process.cgroup metrics #6493
• process add missing metric_types [system][process] Add metric_type metadata for object fields, set stack restriction to 8.9.0 version #7660
• enable TSDB on process - [system][process] Enable tsdb for process datastream #7672
• enable TSDB on core - [System][core] Enable tsdb #8637

Found issues:

• missing time_series_metric [Fleet] Mapping does not reflect the fields definition in package kibana#160403
• TSDB: numbers that are mapped as keyword are not validated correctly at routing time elasticsearch#96552