Quiet hours
Prevent CertShield from paging you in the middle of the night without losing any alerts.
Quiet hours let you tell CertShield “don’t interrupt me between these times.” Alerts that would have fired during the quiet window are held and delivered as soon as the window ends. Nothing is dropped.
Turning quiet hours on
Go to Settings → Quiet Hours. Toggle it on, pick a start and end time, and save. Times are in 24-hour format and interpreted in your selected timezone (see Settings → Preferences for that).
For example: start 22:00, end 07:00. Anything CertShield would have sent between 10pm and 7am is held and delivered at 7am.
What gets held and what doesn’t
Quiet hours apply to alert deliveries, not to scans. CertShield keeps checking your endpoints on the normal schedule — it just doesn’t page you during quiet hours.
Held alerts show up in the Alerts → Event History tab with a Deferred status. You can see exactly what’s waiting to be sent.
When you probably don’t want quiet hours
If you run a 24/7 production service with a rotating on-call, quiet hours will give someone on-call a false sense of quiet. In that case, leave quiet hours off and route critical alerts to a Slack channel that your on-call rotation actually watches.
Quiet hours are a good fit for:
- Solo operators who don’t want to be woken up by a non-urgent warning.
- Teams that already have a separate 24/7 alerting system and use CertShield for the longer-running stuff (expiry warnings, unauthorized issuers).
- Weekly digest workflows where a once-a-day summary is enough.
Emergencies still wait
One thing to be aware of: CertShield’s quiet hours are blunt. An unauthorized issuer alert — which can indicate an ongoing compromise — will sit in the queue until the window ends, same as everything else. If you need urgent alerts to always break through, keep quiet hours off and use a quieter channel for non-urgent rules.