Notification Levels #467

New issue

Closed

opened 2026-02-28 01:47:33 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 01:47:33 -05:00

Owner

Originally created by @deathbybandaid on GitHub (Oct 25, 2021).

Is it a duplicated question?
I didn't see it.

Is your feature request related to a problem? Please describe.
No

Say you have an IT department with 3 levels of support:

Level 1) Basic helpdesk, doesn't touch servers.

Level 2) Does some server stuff.

Level 3) Works on server tickets that get escalated.

Level 4 Department Manager) Shouldn't see tickets from below levels unless they really escalate to this level.

Now imagine you have notifications for different services for different levels of support.

So the feature request is to designate when to automatically escalate to another notification:

Server can't ping 3 times, Level2.

Server still isn't pinging 10 minutes later, Level3.

Server is still down after 30 minutes, notify department manager to check on.

Originally created by @deathbybandaid on GitHub (Oct 25, 2021). **Is it a duplicated question?** I didn't see it. **Is your feature request related to a problem? Please describe.** No Say you have an IT department with 3 levels of support: Level 1) Basic helpdesk, doesn't touch servers. Level 2) Does some server stuff. Level 3) Works on server tickets that get escalated. Level 4 Department Manager) Shouldn't see tickets from below levels unless they really escalate to this level. Now imagine you have notifications for different services for different levels of support. So the feature request is to designate when to automatically escalate to another notification: Server can't ping 3 times, Level2. Server still isn't pinging 10 minutes later, Level3. Server is still down after 30 minutes, notify department manager to check on.

deekerman

2026-02-28 01:47:33 -05:00

closed this issue
added the
feature-request

A:notifications
labels

deekerman commented

2026-02-28 01:47:38 -05:00

Author

Owner

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

Duplicate of #478, focusing any additions in #233

@deefdragon commented on GitHub (Oct 25, 2021): Duplicate of #478, focusing any additions in #233

deekerman commented

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

Author

Owner

@CommanderStorm commented on GitHub (Jul 27, 2023):

I think this should be handled in a dedicated App like https://github.com/louislam/uptime-kuma/pull/2783
Let's not overcomplicate this

@CommanderStorm commented on GitHub (Jul 27, 2023): I think this should be handled in a dedicated App like https://github.com/louislam/uptime-kuma/pull/2783 Let's not overcomplicate this

deekerman commented

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

Author

Owner

@CommanderStorm commented on GitHub (Dec 4, 2023):

@deathbybandaid
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #1315 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
⇒ I am going to close this as a duplicate.

@CommanderStorm commented on GitHub (Dec 4, 2023): @deathbybandaid We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in #1315 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo) ⇒ I am going to close this as a duplicate.