Notification rollout / deferred notifications / severity paging. #267

New issue

Closed

opened 2026-02-28 01:40:50 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 01:40:50 -05:00

Owner

Originally created by @jtagcat on GitHub (Sep 25, 2021).

Relatedish: #233

Service is marked down by uptime-kuma
First notification gets sent to channel a
(optional) ping the last highest notifier (chan a) few minutes before the next step
After n time, send notification to channel b
(optional) ping the last highest notifier (chan b) few minutes before raising severity
After n time, send notification to channel c

This is basic paging, raise severity, notify more channels/people/groups if problem isn't resolved.

Extra feature: allowing to easily change the notifications via API (in real time, possible dependency failure) or scheduling: on workdays, order is a-b-c, on weekends b-a-c, on 2021-09-25 09:00-17:00 d-e, and so on.

Originally created by @jtagcat on GitHub (Sep 25, 2021). Relatedish: #233 1. Service is marked down by uptime-kuma 2. First notification gets sent to channel a 3. (optional) ping the last highest notifier (chan a) few minutes before the next step 4. After n time, send notification to channel b 5. (optional) ping the last highest notifier (chan b) few minutes before raising severity 6. After n time, send notification to channel c This is basic paging, raise severity, notify more channels/people/groups if problem isn't resolved. - Extra feature: allowing to easily change the notifications via API (in real time, possible dependency failure) or scheduling: on workdays, order is a-b-c, on weekends b-a-c, on 2021-09-25 09:00-17:00 d-e, and so on.

deekerman

2026-02-28 01:40:50 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 01:40:55 -05:00

Author

Owner

@deefdragon commented on GitHub (Oct 10, 2021):

I think Adding conditions on when to send notifications would likely be the best way to do this.
IE Degraded Connection for, Down for, Uptime below, etc.

If not paired to the notification, and done individually, you would be able to set multiple conditions for each notification so that you can have the step 3 and 5. This could potentially tie in to sending repeat notifications like asked for in #594 and #233 .

@deefdragon commented on GitHub (Oct 10, 2021): I think Adding conditions on when to send notifications would likely be the best way to do this. IE Degraded Connection for, Down for, Uptime below, etc. If not paired to the notification, and done individually, you would be able to set multiple conditions for each notification so that you can have the step 3 and 5. This could potentially tie in to sending repeat notifications like asked for in #594 and #233 .

deekerman commented

2026-02-28 01:40:55 -05:00

Author

Owner

@louislam commented on GitHub (Oct 14, 2021):

I think Adding conditions on when to send notifications would likely be the best way to do this. IE Degraded Connection for, Down for, Uptime below, etc.

If not paired to the notification, and done individually, you would be able to set multiple conditions for each notification so that you can have the step 3 and 5. This could potentially tie in to sending repeat notifications like asked for in #594 and #233 .

Thanks for finding similar issue.

Should focus in #233.

@louislam commented on GitHub (Oct 14, 2021): > I think Adding conditions on when to send notifications would likely be the best way to do this. IE Degraded Connection for, Down for, Uptime below, etc. > > If not paired to the notification, and done individually, you would be able to set multiple conditions for each notification so that you can have the step 3 and 5. This could potentially tie in to sending repeat notifications like asked for in #594 and #233 . Thanks for finding similar issue. Should focus in #233.