starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Add Customizable Notifications with Service Status and Ping Details in Uptime Kuma #3907

New issue

Closed

opened 2026-02-28 03:44:45 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 03:44:45 -05:00

Owner

Originally created by @NEVARLeVrai on GitHub (Jan 16, 2025).

The notification system in Uptime Kuma could be significantly improved by allowing users to:

Customize the content of notifications based on specific service statuses (e.g., "Down," "Up," "Maintenance").
Define custom messages for each type of service status, enabling tailored communication with users or teams.
Configure notifications to include real-time details like ping results, providing a snapshot of the service's status without requiring access to the main panel.

🏷️ Feature Request Type

Notification system

🔖 Feature description

Add the ability to customize notifications based on the type of service status (e.g., "Down," "Up," "Maintenance") and allow personalized message content for each type of status.

✔️ Solution

In my use case, I would like to:

To implement this feature, the following functionality could be added to Uptime Kuma:

Customizable Notification Templates:

Allow users to define unique notification messages for each type of service status:
Example for "Down": "Service is currently down. Last response time: {ping} ms."
Example for "Up": "Service is back online. Response time: {ping} ms."
Example for "Maintenance": "Service is in maintenance mode. Expected downtime: {time}."
Support dynamic placeholders like {ping}, {status}, {time}, or {probe_name} to make messages more informative.

Ping Update Notifications:

Add an option for periodic notifications that send ping results and the current service status at regular intervals (e.g., every 5 minutes).
Example message: "Service is operational. Average ping: 42 ms over the last 5 minutes."
Users can configure the frequency of these updates.

Notification Filters:

Allow users to choose the types of notifications they want to receive (e.g., "only Down/Up," "include periodic updates").
Add a toggle to enable or disable periodic ping updates independently of status-change notifications.

❓ Alternatives

Currently, Uptime Kuma's notification system is limited to sending alerts when a service goes "Down" and "Up" again. While useful, this lacks flexibility and does not provide continuous monitoring insights (e.g., periodic ping results).

💡 Example Use Case

This improvement would benefit:

IT Teams: Quickly assess service status and latency directly from notifications without accessing the Uptime Kuma panel.
Clients: Provide stakeholders with tailored notifications about maintenance or outages, improving transparency.

Originally created by @NEVARLeVrai on GitHub (Jan 16, 2025). ### 📑 I have found these related issues/pull requests The notification system in Uptime Kuma could be significantly improved by allowing users to: - Customize the content of notifications based on specific service statuses (e.g., "Down," "Up," "Maintenance"). - Define custom messages for each type of service status, enabling tailored communication with users or teams. - Configure notifications to include real-time details like ping results, providing a snapshot of the service's status without requiring access to the main panel. ### 🏷️ Feature Request Type Notification system ### 🔖 Feature description Add the ability to customize notifications based on the type of service status (e.g., "Down," "Up," "Maintenance") and allow personalized message content for each type of status. ### ✔️ Solution In my use case, I would like to: To implement this feature, the following functionality could be added to Uptime Kuma: Customizable Notification Templates: - Allow users to define unique notification messages for each type of service status: - Example for "Down": "Service is currently down. Last response time: {ping} ms." - Example for "Up": "Service is back online. Response time: {ping} ms." - Example for "Maintenance": "Service is in maintenance mode. Expected downtime: {time}." - Support dynamic placeholders like {ping}, {status}, {time}, or {probe_name} to make messages more informative. Ping Update Notifications: - Add an option for periodic notifications that send ping results and the current service status at regular intervals (e.g., every 5 minutes). - Example message: "Service is operational. Average ping: 42 ms over the last 5 minutes." - Users can configure the frequency of these updates. Notification Filters: - Allow users to choose the types of notifications they want to receive (e.g., "only Down/Up," "include periodic updates"). - Add a toggle to enable or disable periodic ping updates independently of status-change notifications. ### ❓ Alternatives Currently, Uptime Kuma's notification system is limited to sending alerts when a service goes "Down" and "Up" again. While useful, this lacks flexibility and does not provide continuous monitoring insights (e.g., periodic ping results). ### 💡 Example Use Case This improvement would benefit: - IT Teams: Quickly assess service status and latency directly from notifications without accessing the Uptime Kuma panel. - Clients: Provide stakeholders with tailored notifications about maintenance or outages, improving transparency.

deekerman

2026-02-28 03:44:45 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 03:44:50 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 16, 2025):

Please see the following

@CommanderStorm commented on GitHub (Jan 16, 2025): Please see the following - https://github.com/louislam/uptime-kuma/issues/508 - #646

deekerman commented

2026-02-28 03:44:50 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 17, 2025):

PS:
Please don't write your issues with AI.
That sucks for readers and does not convey what you want due to duplicates/...

@CommanderStorm commented on GitHub (Jan 17, 2025): PS: Please don't write your issues with AI. That sucks for readers and does not convey what you want due to duplicates/...

deekerman commented

2026-02-28 03:44:50 -05:00

Author

Owner

@NEVARLeVrai commented on GitHub (Jan 17, 2025):

PS:
Please don't write your issues with AI.
That sucks for readers and does not convey what you want due to duplicates/...

I'm not English, I use it to correct my spelling mb

@NEVARLeVrai commented on GitHub (Jan 17, 2025): > PS: > Please don't write your issues with AI. > That sucks for readers and does not convey what you want due to duplicates/... I'm not English, I use it to correct my spelling mb