mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Variable-Based Alert Messages #1074
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#1074
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 @HStep20 on GitHub (May 10, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
Other
🔖 Feature description
This may tie under #21, but it would be great to create alerts using 'Monitor Variables'.
If I have some non-critical systems, I don't want to create an alert for every single one saying: 'website x is down' - Instead It would be awesome if I could create an 'all-encompassing' alert message with something like:
{monitor_nickname} is unavailable on {monitor_group}. Check on it at {monitor_url}✔️ Solution
This would allow you to create generic alerts for groups of systems instead of individual alerts for single monitors. I could build a 'Mission Critical' alert with a different message sent to a text instead of an email, so I get it ASAP, and it would have all the relevant information for context when I receive the alert.
❓ Alternatives
No response
📝 Additional Context
No response
@thimplicity commented on GitHub (Jul 3, 2022):
@HStep20 I came here to look for exactly that feature, thanks
+1
@CommanderStorm commented on GitHub (Aug 4, 2023):
@HStep20
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/975
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^