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

Alerting: Add Equals as a alert condition #19193

Closed
atlasW opened this issue Sep 18, 2019 · 6 comments
Closed

Alerting: Add Equals as a alert condition #19193

atlasW opened this issue Sep 18, 2019 · 6 comments
Labels

Comments

@atlasW
Copy link

atlasW commented Sep 18, 2019

I expect the monitored value to trigger an alarm at 0. So I set the alarm condition of "is within range 0 to 0", but he did not trigger the alarm. So I looked at the code and found that'within range'does not include both sides of the boundary. So if I think it's equal to zero, call the police. How should I set it?

@torkelo
Copy link
Member

torkelo commented Sep 18, 2019

within range and outside range are not inclusive

So right now you would have to do within range -0.01 to 0.01 or something.

@torkelo torkelo changed the title Alert Conditions within's Issue Alerting: Add Equals as a alert condition Sep 18, 2019
@atlasW
Copy link
Author

atlasW commented Sep 19, 2019

within range and outside range are not inclusive

So right now you would have to do within range -0.01 to 0.01 or something.

ok.thanks

@patricktokeeffe
Copy link
Contributor

So right now you would have to do within range -0.01 to 0.01 or something

This workaround requires users to have domain-specific knowledge when deciding what small range constitutes 'zero'.

A 'not equal to" can be achieved using two rules (min is below or max is above), but it is not possible to get a true "equal to" condition. One solution might be:

  • change IS WITHIN RANGE to inclusive
  • but keep IS OUTSIDE RANGE exclusive

I think that's more semantically appropriate for the range labels used.

@bneelon85
Copy link

within range and outside range are not inclusive

So right now you would have to do within range -0.01 to 0.01 or something.

May I ask if or where "not inclusive" is documented? I couldn't find it in the docs and it's not super intuitive, at least for me. May I suggest adding it to the docs and maybe a simple tooltip in the UI when you hover on a selection that indicates this?

Thanks!

@pkolyvas
Copy link
Contributor

We're in the process of moving Grafana feature requests to GitHub Discussions. I'm closing feature requests that have seen limited from the community and/or the Grafana team.

Should this feature still be of interest to you, please re-create it in our Discussions area. In doing so the community can continue to contribute to exploring, confirming and sharing their use cases (and more).

As with all things Grafana, we value your input and participation in this project and appreciate your patience during this transitional period. Should you wish to connect to discuss anything Grafana-related, I have an open door policy and my contact details are on my GitHub profile page.

@Karsonito
Copy link

Please add warning for user in UI if the "IS WITHIN RANGE" threshold chosen with equal values
It's a real problem because of human factor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants