ArafatKhan2198 opened a new pull request, #509:
URL: https://github.com/apache/ozone-site/pull/509

   ## What changes were proposed in this pull request?
   
   Continuing the Recon Web UI documentation restructure started in HDDS-15964, 
this PR adds detailed per-page documentation for the three 
cluster/infrastructure screens of the Recon Web UI.
   
   Previously these screens were only described briefly within the old 
monolithic Web UI page. Each now gets its own dedicated page following the 
standard 9-section format (page overview, when to use, how to access, 
information displayed, available actions, how to interpret, common use cases, 
limitations, and related pages).
   
   New pages added under `01-recon-web-ui/`:
   - `05-datanodes.mdx` — datanode health, operational state, storage, pipeline 
membership, and node removal.
   - `06-pipelines.mdx` — pipeline status, replication, datanode membership, 
and leader-election metrics.
   - `07-containers.mdx` — unhealthy container states, per-state tables, key 
inspection, and CSV export.
   
   The corresponding screenshots are moved into the folder alongside their 
pages. Numbering follows the post-HDDS-15964 layout (Capacity occupies slot 
02), leaving `03`/`04` reserved for the Volumes and Buckets pages in a 
follow-up PR.
   
   ## What is the link to the Apache Jira?
   
   https://issues.apache.org/jira/browse/HDDS-15965
   
   ## How was this patch tested?
   
   Verified locally with the Docusaurus preview. The sidebar validation script 
(`.github/scripts/sidebar.sh`) passes, all image references resolve in their 
new locations, and no dangling links remain.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to