Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
NEVARLeVrai opened this issue Jan 16, 2025 · 3 comments
Labels
feature-request Request for new features to be added

Comments

@NEVARLeVrai
Copy link

NEVARLeVrai commented 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.
@NEVARLeVrai NEVARLeVrai added the feature-request Request for new features to be added label Jan 16, 2025
@NEVARLeVrai NEVARLeVrai changed the title Add Customizable Notifications for Different Service Statuses Add Customizable Notifications with Service Status and Ping Details in Uptime Kuma Jan 16, 2025
@CommanderStorm
Copy link
Collaborator

CommanderStorm commented Jan 17, 2025

@CommanderStorm
Copy link
Collaborator

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

@NEVARLeVrai
Copy link
Author

NEVARLeVrai commented 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features to be added
Projects
None yet
Development

No branches or pull requests

2 participants