3 people 1cf79275cd Honor minimum-reminder-interval for external endpoints (#1773) ...

External endpoints run alerting against a ToEndpoint() copy on every
heartbeat tick and every pushed result. Alert.Triggered survives the
conversion because the Alerts slice elements are shared, but
Endpoint.LastReminderSent lives on the copy: handleAlertsToTrigger
stamped it there and the value was discarded, so the next tick's copy
started from the zero time, time.Since(zero) was always past the
interval, and the alert re-sent on every evaluation —
minimum-reminder-interval was effectively ignored (#1765).

ToEndpoint now carries LastReminderSent over, ExternalEndpoint gains the
field, and both call sites (heartbeat watchdog and the push API) sync it
back alongside the counters they already sync.

Co-authored-by: yzxcj797 <yzxcj797@users.noreply.github.com>

2026-10-04 23:16:37 -04:00

..

alerting_test.go

Honor minimum-reminder-interval for external endpoints (#1773)

2026-10-04 23:16:37 -04:00

alerting.go

fix(alerting): Prevent >2nd reminders from being skipped if the first one triggered

2025-08-26 17:02:30 -04:00

endpoint.go

fix(suites): Load persisted triggered alerts for suite endpoints on start (#1347)

2025-10-20 13:31:58 -04:00

external_endpoint.go

Honor minimum-reminder-interval for external endpoints (#1773)

2026-10-04 23:16:37 -04:00

suite.go

fix(suites): Load persisted triggered alerts for suite endpoints on start (#1347)

2025-10-20 13:31:58 -04:00

watchdog.go

feat(suite): Implement Suites (#1239)

2025-09-05 15:39:12 -04:00