starred/uptime-kuma

Fork 0

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

Add Certificate Expiration Date Variable and Configurable Alerting for Notifications #3769

New issue

Open

opened 2026-02-28 03:40:25 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-28 03:40:25 -05:00

Owner

Originally created by @rvpool on GitHub (Nov 18, 2024).

Proposed Solution:
New Notification Variables:

Add a new variable, {{CERT_EXP_DATE}}, that represents the certificate expiration date.
Add another variable, {{CERT_EXP_DAYS_REMAINING}}, to include the number of days until the certificate expires.
Customizable Alerts for Certificate Expiration:

🏷️ Feature Request Type

Certificate expiry

🔖 Feature description

Allow users to configure notifications for certificate expiration:
Example: Notify 60, 30, 15, and 5 days before the expiration date.
Make this configurable for all monitors, so users don’t have to set it manually for each monitor.
Email Example: Notifications for certificate expiration should include:

Monitor Name (e.g., DonateFood-Prod).
Certificate Name/Hostname (e.g., dsnydonate.nyc.gov).
Expiration Date (e.g., 2025-10-24).
Days Remaining (e.g., 340 days remaining)

Example Email
Subject: Certificate Expiration Alert: DonateFood-Prod
Body:

Monitor: DonateFood-Prod
Certificate Hostname: dsnydonate.nyc.gov
Expiration Date: 2025-10-24
Days Remaining: 30 days
Global Alert Configuration for Certificate Expiry:

✔️ Solution

Add a global configuration option where users can:
Set thresholds for alerts (e.g., notify at 60, 30, 15 days before expiry).
Automatically apply these thresholds to all HTTPS monitors.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @rvpool on GitHub (Nov 18, 2024). ### 📑 I have found these related issues/pull requests Proposed Solution: New Notification Variables: Add a new variable, {{CERT_EXP_DATE}}, that represents the certificate expiration date. Add another variable, {{CERT_EXP_DAYS_REMAINING}}, to include the number of days until the certificate expires. Customizable Alerts for Certificate Expiration: ### 🏷️ Feature Request Type Certificate expiry ### 🔖 Feature description Allow users to configure notifications for certificate expiration: Example: Notify 60, 30, 15, and 5 days before the expiration date. Make this configurable for all monitors, so users don’t have to set it manually for each monitor. Email Example: Notifications for certificate expiration should include: Monitor Name (e.g., DonateFood-Prod). Certificate Name/Hostname (e.g., dsnydonate.nyc.gov). Expiration Date (e.g., 2025-10-24). Days Remaining (e.g., 340 days remaining) Example Email Subject: Certificate Expiration Alert: DonateFood-Prod Body: - Monitor: DonateFood-Prod - Certificate Hostname: dsnydonate.nyc.gov - Expiration Date: 2025-10-24 - Days Remaining: 30 days Global Alert Configuration for Certificate Expiry: ### ✔️ Solution Add a global configuration option where users can: Set thresholds for alerts (e.g., notify at 60, 30, 15 days before expiry). Automatically apply these thresholds to all HTTPS monitors. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:notifications

A:cert-expiry

labels

2026-02-28 03:40:25 -05:00

deekerman commented

2026-02-28 03:40:27 -05:00

Author

Owner

@apio-sys commented on GitHub (Nov 18, 2024):

I think this is already there. At least for the portion to globally set alerting/notification thresholds for certificate expiration. Have you looked in Settings > Notifications > TLS Certificate Expiry ? Then, on an individual monitor you tick "Certificate Expiry Notification" (and other options on that subject as you see fit) and it will inherit the alerting mechanism.

@apio-sys commented on GitHub (Nov 18, 2024): I think this is already there. At least for the portion to globally set alerting/notification thresholds for certificate expiration. Have you looked in Settings > Notifications > TLS Certificate Expiry ? Then, on an individual monitor you tick "Certificate Expiry Notification" (and other options on that subject as you see fit) and it will inherit the alerting mechanism.

deekerman commented

2026-02-28 03:40:27 -05:00

Author

Owner

@rvpool commented on GitHub (Nov 18, 2024):

hi joris thanks for the quick reply

so on the setting notification i have
notification type :smtp
friendly name : Test-Cert-Exp
in the custom subject i have ( but there is not variable for the cert
expiration date)
Certificate Expiry Alert: {{NAME}} is {{STATUS}}

then on my monitor i check
Certificate Expiry Notification

but when i want to test this to see if works i only get and email

with subject
Certificate Expiry Alert: Test is ⚠️ Test

body message:
Test-Cert-Exp

but not information about the cert

On Mon, Nov 18, 2024 at 2:33 PM Joris Le Blansch @.***>
wrote:

I think this is already there. At least for the portion to globally set
alerting/notification thresholds for certificate expiration. Have you
looked in Settings > Notifications > TLS Certificate Expiry ? Then, on an
individual monitor you tick "Certificate Expiry Notification" (and other
options on that subject as you see fit) and it will inherit the alerting
mechanism.

—
Reply to this email directly, view it on GitHub
https://github.com/louislam/uptime-kuma/issues/5358#issuecomment-2483931929,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNBJW6BVXPO3PGDP56EAOML2BI6HLAVCNFSM6AAAAABSAMG5QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBTHEZTCOJSHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@rvpool commented on GitHub (Nov 18, 2024): hi joris thanks for the quick reply so on the setting notification i have notification type :smtp friendly name : Test-Cert-Exp in the custom subject i have ( but there is not variable for the cert expiration date) Certificate Expiry Alert: {{NAME}} is {{STATUS}} then on my monitor i check Certificate Expiry Notification but when i want to test this to see if works i only get and email with subject Certificate Expiry Alert: Test is ⚠️ Test body message: Test-Cert-Exp but not information about the cert On Mon, Nov 18, 2024 at 2:33 PM Joris Le Blansch ***@***.***> wrote: > I think this is already there. At least for the portion to globally set > alerting/notification thresholds for certificate expiration. Have you > looked in Settings > Notifications > TLS Certificate Expiry ? Then, on an > individual monitor you tick "Certificate Expiry Notification" (and other > options on that subject as you see fit) and it will inherit the alerting > mechanism. > > — > Reply to this email directly, view it on GitHub > <https://github.com/louislam/uptime-kuma/issues/5358#issuecomment-2483931929>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BNBJW6BVXPO3PGDP56EAOML2BI6HLAVCNFSM6AAAAABSAMG5QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBTHEZTCOJSHE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

deekerman commented

2026-02-28 03:40:27 -05:00

Author

Owner

@rvpool commented on GitHub (Nov 19, 2024):

hi louis,

This is what I meant regarding certificate alerts.

Currently, when I set up an alert that applies to all my monitors, I also
have the certificate expiry notification checked for each monitor. However,
when I receive the alerts, this is what happens: I get a message for the
up/down status, but the subject is created using the alert's friendly name,
which I set up.

What I’m trying to say is that we need separate alerts—one dedicated to
certificate expiration and another for the up/down status. For the
certificate alert, it should allow me to configure notifications for 30,
60, or 90 days prior to expiration.

Let me know your thoughts on this.

[image: image.png]

On Mon, Nov 18, 2024 at 2:41 PM Rafael Vanderpool @.***>
wrote:

hi joris thanks for the quick reply

so on the setting notification i have
notification type :smtp
friendly name : Test-Cert-Exp
in the custom subject i have ( but there is not variable for the cert
expiration date)
Certificate Expiry Alert: {{NAME}} is {{STATUS}}

then on my monitor i check
Certificate Expiry Notification

but when i want to test this to see if works i only get and email

with subject
Certificate Expiry Alert: Test is ⚠️ Test

body message:
Test-Cert-Exp

but not information about the cert

On Mon, Nov 18, 2024 at 2:33 PM Joris Le Blansch @.***>
wrote:

I think this is already there. At least for the portion to globally set
alerting/notification thresholds for certificate expiration. Have you
looked in Settings > Notifications > TLS Certificate Expiry ? Then, on an
individual monitor you tick "Certificate Expiry Notification" (and other
options on that subject as you see fit) and it will inherit the alerting
mechanism.

—
Reply to this email directly, view it on GitHub
https://github.com/louislam/uptime-kuma/issues/5358#issuecomment-2483931929,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNBJW6BVXPO3PGDP56EAOML2BI6HLAVCNFSM6AAAAABSAMG5QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBTHEZTCOJSHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@rvpool commented on GitHub (Nov 19, 2024): hi louis, This is what I meant regarding certificate alerts. Currently, when I set up an alert that applies to all my monitors, I also have the certificate expiry notification checked for each monitor. However, when I receive the alerts, this is what happens: I get a message for the up/down status, but the subject is created using the alert's friendly name, which I set up. What I’m trying to say is that we need separate alerts—one dedicated to certificate expiration and another for the up/down status. For the certificate alert, it should allow me to configure notifications for 30, 60, or 90 days prior to expiration. Let me know your thoughts on this. [image: image.png] [image: image.png] On Mon, Nov 18, 2024 at 2:41 PM Rafael Vanderpool ***@***.***> wrote: > hi joris thanks for the quick reply > > so on the setting notification i have > notification type :smtp > friendly name : Test-Cert-Exp > in the custom subject i have ( but there is not variable for the cert > expiration date) > Certificate Expiry Alert: {{NAME}} is {{STATUS}} > > then on my monitor i check > Certificate Expiry Notification > > but when i want to test this to see if works i only get and email > > with subject > Certificate Expiry Alert: Test is ⚠️ Test > > body message: > Test-Cert-Exp > > > but not information about the cert > > On Mon, Nov 18, 2024 at 2:33 PM Joris Le Blansch ***@***.***> > wrote: > >> I think this is already there. At least for the portion to globally set >> alerting/notification thresholds for certificate expiration. Have you >> looked in Settings > Notifications > TLS Certificate Expiry ? Then, on an >> individual monitor you tick "Certificate Expiry Notification" (and other >> options on that subject as you see fit) and it will inherit the alerting >> mechanism. >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/louislam/uptime-kuma/issues/5358#issuecomment-2483931929>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/BNBJW6BVXPO3PGDP56EAOML2BI6HLAVCNFSM6AAAAABSAMG5QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBTHEZTCOJSHE> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

deekerman commented

2026-02-28 03:40:28 -05:00

Author

Owner

@jazaragosa commented on GitHub (Jan 30, 2025):

It would be helpful to separate alerts for service uptime/downtime and certificate expiration, especially since there will end of [support for expiration notification emails https://letsencrypt.org/2025/01/22/ending-expiration-emails/ . This way, notifications remain clear and focused on their respective concerns.

@jazaragosa commented on GitHub (Jan 30, 2025): It would be helpful to separate alerts for service uptime/downtime and certificate expiration, especially since there will end of [support for expiration notification emails [https://letsencrypt.org/2025/01/22/ending-expiration-emails/](url) . This way, notifications remain clear and focused on their respective concerns.