From 6fe207a094d597c4ec1432ba459c3b9cf424e5f8 Mon Sep 17 00:00:00 2001 From: rcourtman Date: Sun, 21 Dec 2025 18:34:51 +0000 Subject: [PATCH] refactor: only show critical/warning patrol findings Filter out 'watch' and 'info' severity findings from the API response. These lower-severity findings were mostly noise: - 'watch': CPU is 35% instead of 11% (who cares) - 'info': Stopped container exists (knew that) Now only showing actionable findings: - critical: Something is broken NOW - warning: Something needs attention soon Users prefer silence to noise. --- internal/ai/patrol.go | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/internal/ai/patrol.go b/internal/ai/patrol.go index 15e8799..db9e057 100644 --- a/internal/ai/patrol.go +++ b/internal/ai/patrol.go @@ -1359,8 +1359,10 @@ func (p *PatrolService) GetRunHistory(limit int) []PatrolRunRecord { } // GetAllFindings returns all active findings sorted by severity +// Only returns critical and warning findings - watch/info are filtered out as noise func (p *PatrolService) GetAllFindings() []*Finding { - findings := p.findings.GetActive(FindingSeverityInfo) + findings := p.findings.GetActive(FindingSeverityWarning) + // Sort by severity (critical first) then by time severityOrder := map[FindingSeverity]int{