# Uptime alert recovers even though host is still down

**URL:** <https://discuss.elastic.co/t/uptime-alert-recovers-even-though-host-is-still-down/348866>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [December 8, 2023, 8:32am UTC](https://discuss.elastic.co/t/uptime-alert-recovers-even-though-host-is-still-down/348866 "2023-12-08T08:32:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Glychee](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@Glychee](https://discuss.elastic.co/u/Glychee)\
**Post date:** [December 8, 2023, 8:32am UTC](https://discuss.elastic.co/t/uptime-alert-recovers-even-though-host-is-still-down/348866/1 "2023-12-08T08:32:51Z")

</div>

Running Elasticsearch 8.2.3 and heartbeat 8.2

We've installed heartbeat on a server(manual install) which is polling multiple hosts every 30 seconds and sending the data to Elasticsearch, this data comes in at a steady pace.

After this, we've created an alerting rule that checks every minute if in the last 180 seconds a monitor was down for 3 or more documents.

When adding a non-existing host to our heartbeat, the host correctly is detected as "down" by the alert but occasionally changes to "recovered" and then goes "down" again immediately.

Is there a configuration change I can do so it doesn't recover when it shouldn't?

---

<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:** [January 5, 2024, 8:33am UTC](https://discuss.elastic.co/t/uptime-alert-recovers-even-though-host-is-still-down/348866/2 "2024-01-05T08:33:17Z")

</div>

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