Decouple SSL expiry alerts from Up/Down alerts #2077

New issue

Closed

opened 2026-02-28 02:42:14 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 02:42:14 -05:00

Owner

Originally created by @ligouras on GitHub (Apr 5, 2023).

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

It would be extremely helpful to be able to configure a notification ONLY for certificate expiration alerts, either per monitor, or as a global.

✔️ Solution

Add an option in Settings > Notifications for configuring a notification specifically for certification expiry alerts.

❓ Alternatives

No response

📝 Additional Context

Right now we have a single Slack channel which receives all alerts, and it is hard to detect certificate-related alerts among all up/down events.

Originally created by @ligouras on GitHub (Apr 5, 2023). ### ⚠️ 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 It would be extremely helpful to be able to configure a notification ONLY for certificate expiration alerts, either per monitor, or as a global. ### ✔️ Solution Add an option in Settings > Notifications for configuring a notification specifically for certification expiry alerts. ### ❓ Alternatives _No response_ ### 📝 Additional Context Right now we have a single Slack channel which receives all alerts, and it is hard to detect certificate-related alerts among all up/down events.

deekerman

2026-02-28 02:42:14 -05:00

closed this issue
added the
feature-request

A:notifications

A:cert-expiry
labels

deekerman commented

2026-02-28 02:42:20 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 8, 2023):

@ligouras @ass
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/508 as this is included there
⇒ I am going to close this as a duplicate.

@CommanderStorm commented on GitHub (Dec 8, 2023): @ligouras @ass We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/508 as this is included there ⇒ I am going to close this as a duplicate.

deekerman referenced this issue

2026-02-28 02:49:30 -05:00

Error on long reponse time #2289