mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Ability to blanket disable a notification method #3945
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3945
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @orangehand on GitHub (Feb 1, 2025).
📑 I have found these related issues/pull requests
x
🏷️ Feature Request Type
Settings
🔖 Feature description
Please add a method in the settings>notification to blanket disable a method across all existing monitors. Maybe unless it is the only one being used?
Thanks
✔️ Solution
x
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Apr 17, 2025):
Could you explain the workflow where this would assist you?
In my mind, you either want to
@husjon commented on GitHub (Jan 29, 2026):
Recently I started looking thinking about this myself for my own instance as I'm in the process of switching from one provider to another.
For me at least, I'm thinking the following scenario:
Assume we have an Uptime Kuma instance with 2 existing notification providers set up (e.g. Telegram and Slack)
We'd like to replace one of them for another (e.g. Telegram for Signal)
We'd like to have a test-period where all 3 are up, and after some time another test-period where we disable the one mentioned above while retaining the configuration so that in case it should cause issues, it can be re-enabled, then finally if all is working as expected the notification provider can be disabled.
Since there is already a Apply on all existing monitors, being able to Apply the disabled state to all existing would be a nice addition.

Alternatively, adding an Enabled state to the notification provider itself where if it is disabled, the notification provider is not acted upon at all when a monitor changes state and is not listed in the monitors notifications list.

Hope this makes sense.