fix(heartbeat): 恢復 30 分鐘心跳報告到 SRE 戰情室

2026-04-15 停用理由(forwarded_to_separate_group)有誤,
SRE 戰情室就是 SRE_GROUP_CHAT_ID,不應停用。
恢復 start_heartbeat_monitor(interval=30min)。

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
OG T
2026-04-16 03:05:01 +08:00
parent 5ee76dc30d
commit 62e2efda85

View File

@@ -230,14 +230,17 @@ async def lifespan(_app: FastAPI) -> AsyncGenerator[None, None]:
register_all_providers()
logger.info("mcp_providers_registered")
# Phase 6.5: Telegram 心跳監控
# 2026-04-15 ogt: 停用 — 心跳已轉發到另一個 Telegram 群組,不需在此頻道重複發送
# if settings.OPENCLAW_TG_BOT_TOKEN:
# await telegram_gw.start_heartbeat_monitor(
# heartbeat_interval_minutes=30,
# silence_threshold_hours=2,
# )
logger.info("telegram_heartbeat_monitor_disabled", reason="forwarded_to_separate_group")
# Phase 6.5: Telegram 心跳監控(每 30 分鐘發送到 SRE 戰情室群組)
# 2026-04-16 ogt + Claude Sonnet 4.6: 恢復 — 使用者確認必須繼續在 SRE 戰情室發送
# 上次停用原因forwarded_to_separate_group有誤群組就是 SRE_GROUP_CHAT_ID
if settings.OPENCLAW_TG_BOT_TOKEN:
await telegram_gw.start_heartbeat_monitor(
heartbeat_interval_minutes=30,
silence_threshold_hours=2,
)
logger.info("telegram_heartbeat_monitor_started", interval_minutes=30)
else:
logger.warning("telegram_heartbeat_monitor_skipped", reason="OPENCLAW_TG_BOT_TOKEN not set")
# Reboot Recovery: Warm-up Redis Working Memory from PostgreSQL
# 2026-04-05 ogt: 重開機後 Redis 清空,從 DB restore 未解決的 incidents