From b78d6ac0fe80ff4fe30ecfe3bea7a4c4cc9724bc Mon Sep 17 00:00:00 2001
From: Andreas Wrede <andreas@wrede.ca>
Date: Fri, 24 Apr 2026 11:29:04 +0200
Subject: [PATCH] Fix RECOVER routing: use consistent level name and route via
 alerted channel

threshold.py was emitting level="RECOVERED" for metric recoveries, which
failed the is_recover check in send_notification (which only matched "RECOVER"),
bypassing _alerted_channels routing and the min_level bypass added in the
previous commit. Changed to "RECOVER" so all recovery paths are consistent.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 hbd/server/threshold.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hbd/server/threshold.py b/hbd/server/threshold.py
index 5496be5..46a2ff7 100644
--- a/hbd/server/threshold.py
+++ b/hbd/server/threshold.py
@@ -948,7 +948,7 @@ class ThresholdChecker:
 
         # Format message
         if new_level == AlertLevel.OK:
-            lvl = "RECOVERED"
+            lvl = "RECOVER"
             message = f"{metric_path} = {display_value} ({old_level.name} -> OK)"
         elif new_level == AlertLevel.WARNING:
             lvl = "WARNING"