Templating of notifications #3099

Closed
opened 2026-02-28 03:17:54 -05:00 by deekerman · 2 comments
Owner

Originally created by @RILuse on GitHub (Feb 5, 2024).

#1

🏷️ Feature Request Type

Other

🔖 Feature description

If possible?

  1. i woul like to costumize telegram events
  2. copying monitors

✔️ Solution

  1. Custom notification editor
  2. add copy button in motitor page

Alternatives

No response

📝 Additional Context

No response

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? 1. i woul like to costumize telegram events 2. copying monitors ### ✔️ Solution 1. Custom notification editor 2. add copy button in motitor page ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
Author
Owner

@apio-sys commented on GitHub (Feb 5, 2024):

For 2. you can already clone an existing monitor.

@apio-sys commented on GitHub (Feb 5, 2024): For 2. you can already clone an existing monitor.
Author
Owner

@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.

@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`](https://github.com/louislam/uptime-kuma/milestone/24): mostly peformance (pagination of important events, mariadb, ...), dopping deprecations, backwards incompatible fixes (remote broweser, bark v2, ..) - [`v2.1`](https://github.com/louislam/uptime-kuma/milestone/40): 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`](https://github.com/louislam/uptime-kuma/milestone/42): 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.
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#3099
No description provided.