Telemetry: TOTAL_INDICES_SIZE need to be a Numeric Metric

[freddyDOTCMS]

Parent Issue

No response

Problem Statement

The TOTAL_INDICES_SIZE is a Metric to return the sum of all the Site Search indices, right now this metric is returning the value as follow: "4.6mb", "1.8gb" or "0b", this is not a numeric value and this is preventing us from run query filtering by the size of the indices that the client are using. For example:

Listing all the client that are using more than 2gb on their Site Search indices.

To turn it as a numeric value so we need to return it on the same unit all the time (maybe mb is the best option)

Also The Metric Snapshot right now has the follow sintax:

{
  stats: [
      { 
         feature :  
         description : 
         category :
         name : 
         value : 
      }
      ...
   ],
   no_numeric_metric_1: [value],
   no_numeric_metric_2: [value],
   ... 
  no_numeric_metric_1: [value] 
}

Inside the stats array are list the numeric Metric and outside are the no numeric metrics, after this change the TOTAL_INDICES_SIZE Metric need to be list inside the stats array on this way this is going to be handle as a Numeric Metric on all the SQL Query that we are using.

Steps to Reproduce

Check any Snapshot field on the PROD Telemetry data base

Acceptance Criteria

• The TOTAL_INDICES_SIZE must be a numeric value and be list on the stats array
• The TOTAL_INDICES_SIZE must return 0 when does not exists any Site Search Index.
• The TOTAL_INDICES_SIZE must return the Size of the Index when exists just one Site Search Index.
• The TOTAL_INDICES_SIZE must return the Sum of the Size of the Index when exists more than one Site Search Index.

The Value must be represent on the Same Unit all the time, it means can not be return as mb sometime and other as gb.
I think the best approched here is use mb

dotCMS Version

latest version of the telemetry plugin

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response