Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] The threshold rule cannot be triggered when the indicator value is "no data" #2697

Open
1 task done
rty813 opened this issue Sep 9, 2024 · 2 comments
Open
1 task done
Labels
bug Something isn't working

Comments

@rty813
Copy link

rty813 commented Sep 9, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

image
As shown in the figure, when there is a value in the "Error Message" column, the "Value Exists" threshold rule can be triggered, but if the "Error Message" column is "No Data", the error threshold cannot be triggered anyway.

That is, the threshold rule I set is "contains(message, "Client")". When there is a value in the error message and it is the value in the screenshot, the threshold rule can be triggered normally. However, if the error message becomes "no data", no error will be reported and the error will not be eliminated.

Expected Behavior

When the indicator value is "no data", the alarm recovery should be triggered. Or the "!exists" threshold should be triggered.

Steps To Reproduce

No response

Environment

HertzBeat version(s):v1.6.0

Debug logs

No response

Anything else?

No response

@tomsun28
Copy link
Contributor

try alarm threshold rule: no value exists
image

@rty813
Copy link
Author

rty813 commented Sep 18, 2024

image
image

This is how I set it now. However, when the "error message" is "no data", it will not trigger an alarm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

2 participants