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

index threshold rule does not work as expected with a threshold below a value #103922

Closed
daverick opened this issue Jun 30, 2021 · 2 comments · Fixed by #105626
Closed

index threshold rule does not work as expected with a threshold below a value #103922

daverick opened this issue Jun 30, 2021 · 2 comments · Fixed by #105626
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting/RuleTypes Issues related to specific Alerting Rules Types Feature:Alerting loe:small Small Level of Effort research Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@daverick
Copy link

Kibana version:
7.13.2
Elasticsearch version:
7.13.2

*Original install method (e.g. download page, yum, from source, etc.):
ECE 2.7.1

Describe the bug:
A index threshold rule with a condition below a value is not active when it should be.
A similar Elasticsearch query rule with a condition below a value is working as expected.

Steps to reproduce:

  1. Create a index threshold type rule on a index with a @timestampfield but no recent data in it. Use a count() over all document and a condition is below 1 over the last 5 minutes.
  2. Save the rule.
  3. Go the the Rule and connectors and look at the created rule. it status is OK

Expected behavior:
the status should be Active

Screenshots (if relevant):
rule configuration where some test data can be seen. no alert was triggered.
Capture d’écran 2021-06-30 à 17 54 01
Errors in browser console (if relevant):
no error in browser or server logs

Any additional context:
The purpose of this rule is detecting when no document are ingested in some index that should continuously received data.
condition is above works as expected.
condition is between as the same problem.

@daverick daverick added the bug Fixes for quality problems that affect the customer experience label Jun 30, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Jun 30, 2021
@dmlemeshko dmlemeshko added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jul 2, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jul 2, 2021
@gmmorris gmmorris added Feature:Alerting Feature:Alerting/RuleTypes Issues related to specific Alerting Rules Types labels Jul 2, 2021
@mikecote
Copy link
Contributor

mikecote commented Jul 7, 2021

Adding to To-Do to research if it's a bug or a no-data scenario. No-data scenario may require more work and re-prioritize.

@mikecote mikecote added the loe:small Small Level of Effort label Jul 12, 2021
@chrisronline chrisronline self-assigned this Jul 13, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting/RuleTypes Issues related to specific Alerting Rules Types Feature:Alerting loe:small Small Level of Effort research Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants