CertForge alerts notify your team when conditions that need attention occur — expiring certificates, pending approvals that have gone stale, or policy violations.Documentation Index
Fetch the complete documentation index at: https://docs.certforge.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Alert types
| Alert type | Triggers when |
|---|---|
cert_expiring | One or more certificates expire within N days |
approval_pending | A certificate request has been waiting for approval longer than N hours |
Configuring rules
Go to Admin → Alerts → Rules to create and manage rules.| Setting | Description |
|---|---|
| Label | Human-readable name (e.g. “30-day expiry warning”) |
| Type | cert_expiring or approval_pending |
| Threshold | Days until expiry, or hours pending |
| Cooldown | Minimum hours between repeat notifications for the same condition |
| Trust Profile filter | Restrict rule to a specific DTP (optional) |
| Enabled | Toggle on/off |
Example rules
How alerts fire
The evaluator runs every 5 minutes. When a rule’s condition is met:- Alert state changes to firing
- All subscribed channels and users are notified
- Alert stays firing until the condition clears
- Cooldown prevents repeat notifications within the configured window
Notification channels
Configure destinations in Admin → Settings → Notifications:| Channel | Notes |
|---|---|
| Email (SMTP) | Sent to the org-wide address(es) set in Admin → Settings |
| Webhook | POST JSON payload to any URL |
| Slack | Incoming Webhook URL |
| PagerDuty | Integration key |
Use the Send Test button after configuring a channel to confirm delivery before relying on it for real alerts.