Notification Settings
Configure how and when the SecureLink platform sends notifications to administrators about system events and alerts.
Prerequisites
Before configuring notifications, ensure that SMTP is properly configured in General Settings. Email notifications require a working SMTP relay.
Alert Channels
SecureLink supports the following notification channels:
| Channel | Description |
|---|---|
| Sends notifications to configured email addresses via SMTP | |
| In-App | Displays notifications in the SecureLink UI notification panel |
Each alert type can be routed to one or both channels depending on your operational needs.
Alert Thresholds
Configure the conditions under which alerts are generated:
Edge Offline Threshold
How long an edge device must be unreachable before an alert is generated. Edges send keepalive heartbeats every 30 seconds.
- Default: 5 minutes
- Recommended range: 2-15 minutes
- Setting this too low may generate false positives during brief network disruptions
Config Sync Failure Retry Count
How many consecutive config sync failures are allowed before an alert fires.
- Default: 3 retries
- Each retry occurs on the next batch sync cycle
- After the threshold is exceeded, an alert is generated and the edge is flagged for investigation
Certificate Expiry Warning
How many days before certificate expiration a warning notification is sent.
- Default: 30 days
- Applies to TLS certificates, MQTT certificates, and edge communication certificates
- Multiple warnings may be sent as the expiry date approaches (e.g., at 30, 14, and 7 days)
Notification Recipients
Configure system-wide alert recipients. These are administrators who receive notifications regardless of which tenant the alert originates from.
- Add recipients by email address
- Recipients must have valid SuperAdmin accounts
- Per-tenant notification preferences can be configured separately by TenantAdmin users within their tenant settings
Start with conservative thresholds and adjust based on your environment. A 5-minute offline threshold works well for most deployments, but high-availability environments may want shorter windows.