hertzbeat
hertzbeat copied to clipboard
apache
[BUG] <Incorrect number of recovery notifications>
Is there an existing issue for this?
- [X] I have searched the existing issues
Current Behavior
如果告警阀值配置为超过3次才警告，当服务正常是，恢复通知应该发出一次通知就行，结果发出了3次
Expected Behavior
恢复通知应该发出一次通知就行，结果发出了3次
Steps To Reproduce
无
Environment
HertzBeat version(s):1.4.2
Debug logs
无
Anything else?
无
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Hi, will you see if the latest image that will be upgraded later still has this problem?
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
I would like to help!
Hi, 我尝试了四种场景都没能复现您所说的情况。
1、设置告警【触发次数】为3，且开启【恢复通知】，配置如下图所示：
触发告警后，服务恢复正常只会收到一条【恢复通知】，如下图所示：
2、设置告警【触发次数】为10，此时服务不可用，但在到达触发次数之前，将服务恢复成可用状态，没有收到【恢复通知】
3、针对同一种类型的警告设置多条规则，只会收到一条【恢复通知】
4、针对您截图的HTTP API监控，我用了以下的配置
结果在告警恢复的时候也只收到了一条【恢复通知】
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Can you provide more information, such as whether the docker image is the latest?
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
The latest image has a shameless problem. The problem is with the v1.4.2 image. The version has been noted as v1.4.2.
master分支经本地测试无此问题，docker上的latest镜像也反馈无此问题。请问需要打补丁到1.4.2吗？还是以master分支为准 @tomsun28
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
The master branch has been tested locally without this problem, and the latest image on docker has also been reported to have no such problem. Do I need to patch to 1.4.2? Still based on the master branch @tomsun28
master分支经本地测试无此问题，docker上的latest镜像也反馈无此问题。请问需要打补丁到1.4.2吗？还是以master分支为准 @tomsun28
我们就已master分支为准吧 他应该用的是老的1.4.2镜像 后面有更新了一波现在和latest相同了
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
The master branch has been tested locally without this problem, and the latest image on docker has also been reported to have no such problem. Do I need to patch to 1.4.2? Still based on the master branch @tomsun28
Let's take the master branch as the standard. He should be using the old 1.4.2 surprise. There was a wave of updates later and now it is the same as the latest.
master分支经本地测试无此问题，docker上的latest镜像也反馈无此问题。请问需要打补丁到1.4.2吗？还是以master分支为准 @tomsun28
我们就已master分支为准吧 他应该用的是老的1.4.2镜像 后面有更新了一波现在和latest相同了
好的，感谢解答
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
The master branch has been tested locally without this problem, and the latest image on docker has also been reported to have no such problem. Do I need to patch to 1.4.2? Still refer to the master branch @tomsun28
Let’s refer to the master branch. It should be using the old 1.4.2 image. It has been updated later and is now the same as the latest one.
OK, thanks for the answer