# Uptime Monitor Status not following the greater than logic of the rule

**URL:** <https://discuss.elastic.co/t/uptime-monitor-status-not-following-the-greater-than-logic-of-the-rule/288374>\
**Category:** Synthetics\
**Tags:** elastic-stack-alerting\
**Created:** [November 3, 2021, 10:27pm UTC](https://discuss.elastic.co/t/uptime-monitor-status-not-following-the-greater-than-logic-of-the-rule/288374 "2021-11-03T22:27:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\
**Post date:** [November 3, 2021, 10:27pm UTC](https://discuss.elastic.co/t/uptime-monitor-status-not-following-the-greater-than-logic-of-the-rule/288374/1 "2021-11-03T22:27:22Z")

</div>

Hi All,

Kibana Version: 7.15.1  
Elasticsearch Version: 7.15.1  
Heartbeat Version: 7.15.1

I have a [browser](https://www.elastic.co/guide/en/beats/heartbeat/current/monitor-browser-options.html) monitor configured and sending data to Elasticsearch. This monitor works fine, but I also have an [uptime monitor status rule](https://www.elastic.co/guide/en/observability/7.15/monitor-status-alert.html) configured for this monitor. This rule is fairly simple and is effectively just the base rule that is generated when toggling the uptime enable status alerts toggle. It looks at the `monitor.id` and if `MATCHING MONITORS ARE DOWN` `>` `2` `WITHIN` `LAST 30` `minutes` for the `Status check` then the monitor should fire.

However, the behavior that I am seeing is that instead of the expected `3` or more failures within `30 minutes` triggering the alert, I am seeing that only on a singular (`1`) failure within `30 minutes` this rule will trigger an alert.

I've searched around and have been unable to find anyone else mentioning this. Has anyone else come across this issue?

---

<div class="post-metadata">

**Author:** ![jkambic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkambic/32/53306_2.png) [@jkambic](https://discuss.elastic.co/u/jkambic)\
**Post date:** [November 4, 2021, 2:58pm UTC](https://discuss.elastic.co/t/uptime-monitor-status-not-following-the-greater-than-logic-of-the-rule/288374/2 "2021-11-04T14:58:41Z")

</div>

Hi @BenB196 - thanks for bringing this to our attention. I was able to reproduce this locally using version `7.15` as well. You can track the progress on the resolution of this problem by following [this issue](https://github.com/elastic/kibana/issues/115928), which is for a very similar use case to the one you've described.

---

<div class="post-metadata">

**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\
**Post date:** [November 4, 2021, 4:53pm UTC](https://discuss.elastic.co/t/uptime-monitor-status-not-following-the-greater-than-logic-of-the-rule/288374/3 "2021-11-04T16:53:08Z")

</div>

@jkambic great, thanks for the information, I'll follow along via that issue.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 28, 2021, 4:53pm UTC](https://discuss.elastic.co/t/uptime-monitor-status-not-following-the-greater-than-logic-of-the-rule/288374/4 "2021-11-28T16:53:36Z")

</div>

This topic was automatically closed 24 days after the last reply. New replies are no longer allowed.