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
detection_period propery works wrong #1523
Comments
wrong repo |
HI @dmitrii-khr - actually we prefer Elementary issues to be concentrated in this repo so it's good that you opened it here. I'll close the other one actually. Currently, this is expected behavior, though I understand the confusion. If you'd like to make the test more real-time, you may want to consider decreasing the time bucket from daily to less than that. For example, hourly buckets can be set like this:
Please let me know if this makes sense. |
Describe the bug
I'd like to complain again about the detection_period configuration property.
The following setup
transforms to the following statement in the elementary query which decides whether alert or not alert:
The non-strict condition means that it will alert for 2 days. But it is expected that the alert will be only one 1 day.
Now it is not possible to configure a time series test, to alert it for the current day and not for issues that were yesterday. 0 value causes test failure.
To Reproduce
setup time-series test with bucket size 1 day and detection_period 1 day
Expected behavior
With detection period of 1 day, test will not fail if start date of failed time bucket is more than 24 hours ago.
Condition which detects if test should fail have to be strict:
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: