mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
[ntfy] add priority DOWN field #3676
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#3676
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 @schwalbe13 on GitHub (Oct 19, 2024).
📑 I have found these related issues/pull requests
no related issues.
🏷️ Feature Request Type
Settings
🔖 Feature description
At the moment, I can only define one Priority level for the ntfy notification for when the server is not down (=UP). The DOWN priority has a fixed priority of 5. I want to be able to define a priority type for DOWN as well. Not all DOWN alerts should be sent with the maximum priority.
When I put my phone in "Do Not Disturb" mode, I don't want to be notified when a less important server is DOWN.
✔️ Solution
❓ Alternatives
Using the MQTT notification and modify the alert with python, before sending it to ntfy.
📝 Additional Context
No response