Arun Sarin created HDDS-15147:
---------------------------------
Summary: [Cluster Capacity] Standardize Datanode Insight Export
Filenames and Unit Headers
Key: HDDS-15147
URL: https://issues.apache.org/jira/browse/HDDS-15147
Project: Apache Ozone
Issue Type: Bug
Components: Ozone Recon
Reporter: Arun Sarin
h3. *Summary*
Currently, the "Download Insights" feature on the Datanodes dashboard produces
a file with a generic name and lacks unit indicators in the column headers.
This makes it difficult to distinguish between exports from different clusters
and leads to ambiguity when interpreting storage metrics (e.g., Capacity, Used
Space).
h3. *Problem Description*
# *Non-descriptive Filenames:* The downloaded file lacks a unique identifier.
In environments with multiple clusters or recurring monitoring tasks, users
cannot distinguish which file belongs to which environment without opening them.
# *Ambiguous Metrics:* The spreadsheet headers (e.g., Filesystem Capacity,
Ozone Used Space) do not specify units. As seen in the provided sheet, values
are large integers (bytes), which are difficult to read and verify against the
UI (which shows {*}GB{*}) without manual conversion.
h3. *Proposed Improvements*
h4. *1. Standardize Filename Convention*
Incorporate the cluster name or CM hostname and a timestamp into the filename
to ensure uniqueness and traceability.
* *Suggested Format:* Datanode_Insights_[ClusterName]_[YYYYMMDD_HHMM].csv
* *Example:* Datanode_Insights_ccycloud-3_20240520_1430.csv
h4. *2. Explicit Unit Headers*
Update the export logic to include the unit of measurement in the column
headers. Since the raw data is currently exported in bytes, the headers should
reflect this to prevent calculation errors.
* *Current Header:* Filesystem Capacity
* *Recommended Header:* Filesystem Capacity (Bytes) or Filesystem Capacity
(GB) _if the data is pre-converted._
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
