告警没有按照告警频率和持续时长进行产生

[KerwinChen]

前端版本：5.14.2
后端版本：v5.14.2-f8ac0a9b4ad9657b71b34a200b42a80e474d71d6

在告警规则中设置了告警频率60秒，持续时长180秒（根据系统描述，我理解应该是在180秒内，3次探测失败才会产生告警）

但是当前遇到的情况是，在第一次探测（60秒）失败的时候就产生了告警，在第二次探测（120秒）成功的时候恢复告警。

理论上这两条告警（一条告警一条恢复）不应该产生不是吗？
是我哪里配置失误了吗？

[UlricQin]

你可以打开 n9e-server 的DEBUG级别的日志，看看规则判断的时候，查到了什么数据。你上面的截图不足以佐证你的推论。

[KerwinChen]

2022/12/01 10:48:06 �[32m/home/runner/work/nightingale/nightingale/src/models/alerting_engine.go:92 �[33mSLOW SQL >= 200ms
�[0m�[31;1m[1146.303ms] �[33m[rows:1]�[35m UPDATE `alerting_engines` SET `clock`=1669862885,`cluster`='Default' WHERE instance='n9e:19000'�[0m
2022-12-01 10:53:36.998834 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe triggered) push_queue: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669863216 
2022-12-01 10:53:37.070242 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe triggered) consume: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669863216 
2022-12-01 10:53:37.077224 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe triggered) notify: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669863216 
2022-12-01 10:53:37.323187 INFO sender/dingtalk.go:76 dingtalk_sender: result=succ url=https://oapi.dingtalk.com/robot/send?access_token= code=200 response={"errcode":0,"errmsg":"ok"}
2022-12-01 10:53:38.086570 INFO sender/wecom.go:42 wecom_sender: result=succ url=https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=3dc9185f-3888-475c-a2b1- code=200 response={"errcode":0,"errmsg":"ok"}
2022-12-01 10:54:37.002874 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe recovered) push_queue: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669863216 
2022-12-01 10:54:37.027025 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe recovered) consume: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669863216 
2022-12-01 10:54:37.032402 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe recovered) notify: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669863216 
2022-12-01 10:54:37.200648 INFO sender/dingtalk.go:76 dingtalk_sender: result=succ url=https://oapi.dingtalk.com/robot/send?access_token= code=200 response={"errcode":0,"errmsg":"ok"}
2022-12-01 10:54:37.391936 INFO sender/wecom.go:42 wecom_sender: result=succ url=https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=3dc9185f-3888-475c-a2b1- code=200 response={"errcode":0,"errmsg":"ok"}

2022-12-01 11:03:37.052923 INFO engine/logger.go:19 event(37111b9d3a468747280c6f0afb8cb74d triggered) push_queue: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.13]1@1669863817 
2022-12-01 11:03:37.134147 INFO engine/logger.go:19 event(37111b9d3a468747280c6f0afb8cb74d triggered) consume: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.13]1@1669863817 
2022-12-01 11:03:37.140800 INFO engine/logger.go:19 event(37111b9d3a468747280c6f0afb8cb74d triggered) notify: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.13]1@1669863817 
2022-12-01 11:03:37.398717 INFO sender/dingtalk.go:76 dingtalk_sender: result=succ url=https://oapi.dingtalk.com/robot/send?access_token= code=200 response={"errcode":0,"errmsg":"ok"}
2022-12-01 11:03:37.834725 INFO sender/wecom.go:42 wecom_sender: result=succ url=https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=3dc9185f-3888-475c-a2b1- code=200 response={"errcode":0,"errmsg":"ok"}
2022-12-01 11:04:37.058558 INFO engine/logger.go:19 event(37111b9d3a468747280c6f0afb8cb74d recovered) push_queue: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.13]1@1669863817 
2022-12-01 11:04:37.085231 INFO engine/logger.go:19 event(37111b9d3a468747280c6f0afb8cb74d recovered) consume: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.13]1@1669863817 
2022-12-01 11:04:37.090293 INFO engine/logger.go:19 event(37111b9d3a468747280c6f0afb8cb74d recovered) notify: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.13]1@1669863817 
2022-12-01 11:04:37.209234 INFO sender/dingtalk.go:76 dingtalk_sender: result=succ url=https://oapi.dingtalk.com/robot/send?access_token= code=200 response={"errcode":0,"errmsg":"ok"}
2022-12-01 11:04:37.423162 INFO sender/wecom.go:42 wecom_sender: result=succ url=https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=3dc9185f-3888-475c-a2b1- code=200 response={"errcode":0,"errmsg":"ok"}
2022-12-01 11:06:28.647336 WARNING writer/writer.go:79 post to http://127.0.0.1:9090/api/v1/write got error: push data with remote write request got status code: 400, response body: out of order sample
2022-12-01 11:06:28.647466 WARNING writer/writer.go:80 example timeseries:labels:<name:"__name__" value:"disk_total" > labels:<name:"ident" value:"" > labels:<name:"product" value:"" > labels:<name:"ability" value: samples:<value:5.2710309888e+10 timestamp:1669864140534 > 
2022-12-01 11:07:37.072956 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe triggered) push_queue: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669864057 
2022-12-01 11:07:37.134458 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe triggered) consume: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669864057 
2022-12-01 11:07:37.140324 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe triggered) notify: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669864057 
2022-12-01 11:07:37.449864 INFO sender/dingtalk.go:76 dingtalk_sender: result=succ url=https://oapi.dingtalk.com/robot/send?access_token= code=200 response={"errcode":0,"errmsg":"ok"}
2022-12-01 11:07:37.838310 INFO sender/wecom.go:42 wecom_sender: result=succ url=https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=3dc9185f-3888-475c-a2b1- code=200 response={"errcode":0,"errmsg":"ok"}
2022-12-01 11:08:37.076797 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe recovered) push_queue: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669864057 
2022-12-01 11:08:37.087072 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe recovered) consume: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669864057 
2022-12-01 11:08:37.092996 INFO engine/logger.go:19 event(43c80d8ca9ad2acdcad565759a6b47fe recovered) notify: rule_id=10 [__name__=ping_result_code ident=n9e product=important region=nic rulename=PING - 重要地址探测失败 target=10.0.254.12]1@1669864057 
2022-12-01 11:08:37.202189 INFO sender/dingtalk.go:76 dingtalk_sender: result=succ url=https://oapi.dingtalk.com/robot/send?access_token= code=200 response={"errcode":0,"errmsg":"ok"}
2022-12-01 11:08:37.438323 INFO sender/wecom.go:42 wecom_sender: result=succ url=https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=3dc9185f-3888-475c-a2b1- code=200 response={"errcode":0,"errmsg":"ok"}

有查过日志，在那个时间点（10:53:36、11:07:37）前确实没有其他日志了。