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

   ## What changes were proposed in this pull request?
   
   This PR adds two design documents under 
`docs/07-system-internals/08-design/` for a proposed **Diagnose** feature in 
Recon.
   
   When a background pipeline such as deletion slows down or stops, finding the 
cause today means knowing many metrics across OM, SCM and the Datanodes, and 
which of them only move on the leader. Dashboards show the raw data but don't
   say whether a flat line is healthy, an intentional pause or a real stall.
   
   - **Recon Diagnosis Framework** (`recon-diagnosis-framework.md`) describes a 
framework that lets Recon answer three questions for a chosen service: where it 
stops making progress, what evidence shows this (each item comes with the 
PromQL query that produced it), and what to do next. It covers:
     - the REST API `GET /api/v1/diagnose`, with one URL that serves both 
browsers and scripts;
     - the `DiagnosisProvider` plug-in interface;
     - how the verdict and the confidence level are chosen;
     - principles for writing rules;
     - a step-by-step guide to adding a diagnosis for a new service;
     - the UI, cost limits, failure handling, security, configuration and 
alternatives considered.
   
     The framework adds no new metrics, RPCs, protobuf messages or RocksDB 
tables, and Recon keeps no state.
   - **Recon Diagnosis: Deletion** (`recon-diagnosis-deletion.md`) describes 
the first diagnoses built on the framework: `OMDeletionService`, 
`SCMDeletionService` and `DatanodeDeletionService`. For each one it lists the 
rules, panels, facts, thresholds and troubleshooting anchors. It also serves as 
a worked example for adding diagnoses for other services.
   
   ## What is the link to the Apache Jira?
   
   HDDS-17695
   
   ## How was this patch tested?
   
   
   
   


-- 
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