| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| admin | ||
| ai | ||
| assistant | ||
| auth | ||
| clinical-gap | ||
| clinical-signals | ||
| facts | ||
| mcp | ||
| patient | ||
| persona | ||
| plan | ||
| plan-aggregate | ||
| realtime-coach | ||
| sync | ||
| weixin-aibot |
现象:FRIDAY 每小时报一次 [PAC CRITICAL] push 断流(28.9h / 29.9h 无推送), 但它根本还没正式上线推送。 根因在触发条件 —— 监控只跳过"从未推过"的宿主(!lastPush → continue), 而 FRIDAY 联调期推过几次就停了,于是被当成"已上线、现在挂了"。 "推几次就停"恰恰是联调的正常节奏,不是数据在漏。 加 monitoring.push_lag_alert(默认 true): - FRIDAY manifest 置 false,并写明**正式上线推送后删掉该段即恢复** - 不配 → true,既有宿主行为不变,不会静默失去监控 - 命中时打一行 log(⏸ 已按 manifest 关闭),不是无声跳过 【为什么不用"把阈值调大"】那样语义是"容忍 10 万小时不推",读的人分不出是故意关掉 还是填错了;显式布尔把意图留在 yaml 里,上线时删一行即可。 测试 818 项(+3)。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| admin | Loading commit data... | |
| ai | Loading commit data... | |
| assistant | Loading commit data... | |
| auth | Loading commit data... | |
| clinical-gap | Loading commit data... | |
| clinical-signals | Loading commit data... | |
| facts | Loading commit data... | |
| mcp | Loading commit data... | |
| patient | Loading commit data... | |
| persona | Loading commit data... | |
| plan | Loading commit data... | |
| plan-aggregate | Loading commit data... | |
| realtime-coach | Loading commit data... | |
| sync | Loading commit data... | |
| weixin-aibot | Loading commit data... |