Skip to content

feat: add root-cause assessment summary to diagnosis output#40

Open
aminalaee wants to merge 3 commits into
mainfrom
feat/assessment
Open

feat: add root-cause assessment summary to diagnosis output#40
aminalaee wants to merge 3 commits into
mainfrom
feat/assessment

Conversation

@aminalaee

Copy link
Copy Markdown
Owner

No description provided.

Reduce fired findings and metrics into a single "Likely bottleneck"
summary, shown before the detailed findings in text output and as a
top-level `assessment` field in JSON. This turns the report from a list
of independent findings into a concise triage of the most likely cause.

The assessment is a read-only reducer over DiagnosisResult: it consumes
rule results (never re-running thresholds), draws its evidence from the
findings that actually fired, and stays conservative — returning "no
clear bottleneck" or low confidence when evidence is weak or conflicting.
Absent traffic metrics are treated as unknown rather than idle.
Only show the "Likely bottleneck" block when there is a real bottleneck
to name — on a clean run it just echoed "no issues detected". Also dedupe
assessment evidence lines that cite the same metric (e.g. waiting
requests reported by several findings), and refresh docs/demo.png to
include the new assessment section.
Add a "Root-cause summary" feature bullet, include the "Likely
bottleneck" section in the example output, and reword the intro to
mention the summary shown above the detailed findings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant