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

[Uptime][Alert][Synthetics] Alert is triggered without matching the rule #115928

Closed
angeliski opened this issue Oct 21, 2021 · 5 comments
Closed
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability

Comments

@angeliski
Copy link

Kibana version:
v 7.15.0
Elasticsearch version:
v 7.15.0
Server OS version:
I don't know because I am using the elastic cloud

Original install method (e.g. download page, yum, from source, etc.):
We used the terraform module

Describe the bug:
We are having some issues with the alert trigger from the uptime module (using the synthetics).
We configured or rule to trigger when we have 3 downs in 10 minutes.

Rule Connector
But the rule is triggered when just 1 down happens

Uptime View

I was trying to find the problem and maybe the alert is not filtering for the field synthetics.type (I believe only heartbeat/summary is relevant in that case, Am I right?)

Kibana Discovery

Steps to reproduce:

  1. Configure a Synthetic test (I am not using fleet, I am running from my cluster and sending the data to elastic)
  2. Configure a rule for alert (maybe 3 downs in 10 minutes) Docs
  3. Make the test break only one time

Expected behavior:
The alert isn't triggered

Any additional context:
I will try to use the filter in the rule to test the synthetics.type solution, maybe that could be a simple workaround

@angeliski angeliski added the bug Fixes for quality problems that affect the customer experience label Oct 21, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 21, 2021
@stratoula stratoula added the Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability label Nov 2, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/uptime (Team:uptime)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 2, 2021
@stratoula stratoula added needs-team Issues missing a team label triage_needed labels Nov 2, 2021
@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 2, 2021
@justinkambic
Copy link
Contributor

I was able to reproduce this locally, thank you for bringing it to our attention.

Steps to repro are just what the description says. Create a browser monitor, configure a Monitor Status rule with n downs within a timespan. When the monitor fails the first time, the rule will become active.

image

image

image

@shahzad31
Copy link
Contributor

we have a PR up to fix this #118999

@justinkambic justinkambic self-assigned this Nov 18, 2021
@justinkambic
Copy link
Contributor

@shahzad31 thanks so much, I missed the overlap between this issue and that PR. Thanks!

@shahzad31
Copy link
Contributor

Fixed by #118999, will be available in 7.16

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 Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability
Projects
None yet
Development

No branches or pull requests

5 participants