mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Templating of notifications #3099
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#3099
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 @RILuse on GitHub (Feb 5, 2024).
📑 I have found these related issues/pull requests
#1
🏷️ Feature Request Type
Other
🔖 Feature description
If possible?
✔️ Solution
❓ Alternatives
No response
📝 Additional Context
No response
@apio-sys commented on GitHub (Feb 5, 2024):
For 2. you can already clone an existing monitor.
@CommanderStorm commented on GitHub (Feb 5, 2024):
Duplicate of https://github.com/louislam/uptime-kuma/issues/646
=> closing as a duplicate
TLDR: this is a considerable issue and currently our priorities are on other issues (release planning is fluid, stuff might or might not make it, additional stuff might get added):
v2.0: mostly peformance (pagination of important events, mariadb, ...), dopping deprecations, backwards incompatible fixes (remote broweser, bark v2, ..)v2.1: fixes and small stuff accrued during 2.0, but also long-awaited features like an API and some new notification providers (SevenIO, WhatsApp)v2.2: user-management, new monitors (slow response time monitoring, zabix trigger, zookeeper) and new notification providers (google chat)To have the liberty to work on the notifications, said system needs better tests first.