fix: recognise alertmanager/coralogix/honeycomb keys in check_evidence_availability

kaushal-bakrania · kaushal-bakrania · commit 7c08add94f23 · 2026-04-19T17:34:06.000+01:00
The same drift class the frozenset fix addressed: _map_* mappers write these keys into the evidence dict, but the has_cloudwatch_evidence OR- chain was not updated alongside. A firing-critical alert from these stacks with a sparse payload (no tracer_web_run, no annotation body) would fall into _handle_insufficient_evidence and skip the reasoning LLM — the mirror image of the short-circuit miss this PR already fixes. Review feedback from Greptile on PR #672.
diff --git a/app/nodes/root_cause_diagnosis/evidence_checker.py b/app/nodes/root_cause_diagnosis/evidence_checker.py
@@ -84,6 +84,11 @@ def check_evidence_availability(
         or evidence.get("eks_deployments") is not None
         or evidence.get("eks_pod_logs") is not None
         or evidence.get("eks_deployment_status") is not None
+        or evidence.get("alertmanager_alerts") is not None
+        or evidence.get("alertmanager_silences") is not None
+        or evidence.get("coralogix_logs") is not None
+        or evidence.get("coralogix_error_logs") is not None
+        or evidence.get("honeycomb_traces") is not None
     )
 
     # Check for evidence in alert annotations or raw text
