What is Notification Management; how do the notification profile, Contact Groups and channels come together?
Short answer
Notification Management is the screen that manages TR7's device-level, event-based alerting infrastructure: system resources (CPU, memory, disk, bandwidth), network status (interface, IP, gateway, VIP), cluster events, the freshness of IP intelligence data, NTP synchronization and user operations are monitored; a notification is sent when a threshold is exceeded or a status changes. The screen consists of four building blocks (core concepts): the notification profile in the Notifications list defines on which event (Notification Type), through which channel (Notification Action: Send e-mail, Send sms, SNMP trap, Notify UI) and to whom (Notification Contacts) the notification is sent; Contact Groups groups the recipients; E-mail Settings defines the SMTP server, and SNMP Settings the trap target. Recommended order: first the channels, then the contact groups, and the profile last.
Where It Is Used in TR7
| Where | Field / label | What for |
|---|---|---|
| Settings → General Settings → Notification Management → Notifications → Add | Name, Notification Type (default User action) | The event type the profile will monitor |
| Same form, Notification event section | Limit, scope fields (Route Table, Network Interface, IP), Log Type or threshold fields | Threshold, scope or user operation filter depending on the event type |
| Same form | Notification Action (default Send e-mail + Notify UI), Notification Contacts | Channels and recipient groups (at least one group) |
| Notification Management → Contact groups → Add | Contact Selection (default By user type; By user; with manual entry, E-mail addresses and Phone numbers) | Grouping the recipients by user type, by user, or with manually entered e-mail addresses and phone numbers |
| Notification Management → E-mail settings / SNMP settings | E-mail Settings, SNMP Settings | Infrastructure of the e-mail and trap channels |
| Settings → System Logs → Notification Logs | Notification Logs | History of the notifications produced |
Channels
| Channel | Prerequisite |
|---|---|
| Send e-mail | E-mail settings (SMTP) defined (What is SMTP; with which settings does TR7 send e-mail notifications?) |
| Send Sms | A phone number on the recipients in Contact groups |
| SNMP Trap | SNMP settings defined (What is SNMP; for what purposes is it used in TR7?) |
| Notify UI | None; the notification appears in the interface's own notification area |
- On a new installation, a ready Admins contact group (users of the Super Admin type) comes together with ready profiles for CPU, memory and disk (90% threshold), VIP, TR7 IP, IP intelligence data (45 days), NTP synchronization (5 seconds) and license status; all of them are bound to the Admins group with the Send e-mail + Notify UI channels (default records).
- vService, WAF, Bot/DDoS and AGS notifications are managed from their own screens and carry their recipients in their own forms; from this screen, only the infrastructure (SMTP server, SNMP target) is used (What are the notification channels (UI, e-mail, SMS, SNMP)?).
- In a cluster, the settings are synchronized to the peer device; each device produces and sends notifications separately for its own events.
Common Misconceptions
- "Contact groups is also used in WAF and vService notifications." The recipients of module notifications are entered in their own forms; Contact groups is used only in the profiles on this screen.
- "If a profile has been defined, the e-mail is sent." For the Send e-mail and SNMP trap channels to work, E-mail settings and SNMP settings are configured first.
- "A deleted ready profile comes back on its own." The ready records are created only at the first installation; a deleted ready profile is not recreated.
How it is done in the documentation
