Prerequisites
Prerequisites
- DevHelm CLI installed or an API token
- An HTTPS endpoint to monitor
Add an SSL expiry assertion
Thessl_expiry assertion checks how many days remain before the TLS certificate expires. Add it to any HTTP monitor:
- Warns at 30 days — time to plan renewal
- Fails at 14 days — urgent action needed
Choosing thresholds
| Threshold | Use case |
|---|---|
| 30 days (warn) | Standard renewal reminder with plenty of lead time |
| 14 days (fail) | Critical alert — certificate is close to expiring |
| 7 days (fail) | Emergency — immediate action required |
Check frequency
Certificate expiry doesn’t change rapidly, so checking every hour (3600) or every 6 hours (21600) is sufficient. This saves check quota while still catching issues promptly.
Combine with other assertions
SSL monitoring works alongside other HTTP assertions:TLS verification
SetverifyTls: true (the default) to also catch invalid certificates, hostname mismatches, and untrusted CAs — the check fails immediately rather than just triggering the expiry assertion.
Set verifyTls: false only for self-signed certificates in development environments.
Next steps
HTTP assertions
Full list of HTTP assertion types.
Alerting guide
Route certificate warnings to specific channels.
Monitors guide
Configure all monitor types.