Variable-Based Alert Messages #1074

Closed
opened 2026-02-28 02:09:07 -05:00 by deekerman · 2 comments
Owner

Originally created by @HStep20 on GitHub (May 10, 2022).

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ 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

Originally created by @HStep20 on GitHub (May 10, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ 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_
deekerman 2026-02-28 02:09:07 -05:00
Author
Owner

@thimplicity commented on GitHub (Jul 3, 2022):

@HStep20 I came here to look for exactly that feature, thanks

+1

@thimplicity commented on GitHub (Jul 3, 2022): @HStep20 I came here to look for exactly that feature, thanks +1
Author
Owner

@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?) ^^

@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?) ^^
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1074
No description provided.