Impacted Service Count Alerts (Report Card Messages) #3878

New issue

Closed

opened 2026-02-28 03:43:56 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 03:43:56 -05:00

Owner

Originally created by @BloodBlight on GitHub (Jan 8, 2025).

This is difficult to search for, but I didn't see anything. Sorry if it's already been request.

🏷️ Feature Request Type

Other

🔖 Feature description

A report card message, or addendum to excising messages stating the total number of services in an impacted state.

✔️ Solution

There are a few ways this could be done:

As an optional addendum to alert messages. "There are now X services in an unhealthy state."
On a timer, say once an hour, if there are any services down, it generates it's own alert with a report card.
A combination of both, a report card is sent after any service state change.

This could be helpful both for management roles, or in my case, I have 50 services go down, 40 recovered, but I need to log in to know there are still 10 down.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @BloodBlight on GitHub (Jan 8, 2025). ### 📑 I have found these related issues/pull requests This is difficult to search for, but I didn't see anything. Sorry if it's already been request. ### 🏷️ Feature Request Type Other ### 🔖 Feature description A report card message, or addendum to excising messages stating the total number of services in an impacted state. ### ✔️ Solution There are a few ways this could be done: - As an optional addendum to alert messages. "There are now X services in an unhealthy state." - On a timer, say once an hour, if there are any services down, it generates it's own alert with a report card. - A combination of both, a report card is sent after any service state change. This could be helpful both for management roles, or in my case, I have 50 services go down, 40 recovered, but I need to log in to know there are still 10 down. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 03:43:56 -05:00

closed this issue
added the
feature-request

duplicate

A:notifications
labels

deekerman commented

2026-02-28 03:44:00 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 8, 2025):

Resending can already be done
The rest is a duplicate of #1534 or at least close enough to be implemented via this
=> Closing as a duplicate

@CommanderStorm commented on GitHub (Jan 8, 2025): Resending can already be done The rest is a duplicate of #1534 or at least close enough to be implemented via this => Closing as a duplicate